rendrag

update: I swapped NICs, and the problem is still occuring. I'm out of ideas. Anyone out there have any suggestions? I'm about ready to kick this whole system to the curb. update #2 I have 2 network switches in this loop. I have a 16 port next to the server (switch A), and a 5 port on my desk that connects 3 PCs (switch B). When I disconnect the uplink cable from B going to A while actively running the software on another desktop (not the one that I'm having problems with), and I would expect it would dump my connection because the link was broken. Suprisingly, it did not. That leads me to believe the issue is more software related. Since I've already uninstalled/reinstalled the software once, I guess it's back to the drawing board. I'm still interested in finding some connection diagnostic software, or whatever it's called, so if anyone has some links, I'd appreciate it. Thanks

Hey fellas, I'm having a disagreement with the support tech for our IBM as/400. On our Windows boxes, we run a terminal emulation program provided by IBM. As of Friday of last week (9/29), I've been experiencing semi-frequent disconnects from the system. It only seemed to drop me when I wasn't actively using the software. I couldn't get a bead on how long I needed to be idle, however. I called support, and it was initially thought that the session timeout was too short, which was why I was getting disconnected. Today, the tune changed. They are now saying it is a problem with my workstation (they didn't provide it, so they won't support it naturally). It's dropping the connection. I've tried uninstalling the software, and also the hardware from device manager, swapping cat5 cable, swapping ports on the switch, and I've had 0 luck. I have a spare 10/100 card I am about to install (waiting for a confirmation from the support company that I won't have any issues because of a new MAC address). Now that you have the background and the troubleshooting I've done, here's the question: is there any software out there (preferably free) that will monitor an adapter and tell me if the connection gets reset, dropped, or what have you? I was thinking something like a bandwidth monitor, but if my connection is idle, and it gets reset, it probably won't notice. Thanks for the help!

are the ports used in the guide the same as what your current version of shoutcast is using? That's the only thing I can think of as to why it wouldn't work

try here: http://www.portforward.com/english/routers...routerindex.htm

go to start > run, and type cmd in the opening. a command window should pop up. If you know the computer name of the other machine, just type ping computer_name If it responds, you should still be able to share folders if you type them in directly to the address bar in Windows Explorer, i.e. \\home_pc\share_1 if you don't know the computer name, at the command prompt, type net view a list of computers on your network should pop up. If nothing happens, then you probably nLite'd too much out for it to function properly on a typical home network. Why did you want to hide yourself anyway if you wanted to share files and folders?

i'd check w/ runescape's tech boards on that... doubtful you'll find as many experienced people here as there

Windows?Seriously though, the only reason I can think as to why you lose internet (but not LAN) connectin is that somehow Windows stops bridging the wireless and wired connections. That would explain why you can still transfer files to the desktop from the wireless laptop, but you can't ping the router. As it has come up in other threads recently, I am not aware of a single person that has set up bridging in XP at all reliably. I just don't think MS put bridging into Windows XP actually thinking anyone would try to use it.

I think it's possible... I fairly certain hotels use something similar to Sputnik or Chillispot If you get a linksys WRT54G v4 or earlier (check ebay), you can load DD-WRT firmware and it will allow you to use the chillispot/sputnik hotspot. I don't know that it won't allow access to network drives, but if it's a seperate access point in your conference room, you might be able to create a seperate vlan on your switch for that AP so that it can't access the rest of the network.

do you have a router or just a single machine? If it's just a single machine, try this. Maybe it will help. http://popular.softlandmark.com/Traffic_Analyzer_l5.html if your traffic goes through a router, then you're router would have to do the analyzing, and I'm guessing no consumer grade router can do that

mind you that Windows service has been disabled by default as of SP2 for XP, and is frequently used by spammers and adware to send pop up messages.

might that pre-n device not work 100% with 802.11g? The driver might be flaky

Are you using the desktop as a wireless access point? I've never had much success with bridging 2 connections in XP. I had connectivity problems as well. I would try starting with no security as takeshi mentioned, and slowly work up.

details would help: what kind of vpn software are you using?

well, you don't need to know the IP when you use VNC, just the computer name. But once you set up the router ports, you shouldn't need to maintain it. you could also look at pcAnywhere.

It's not very secure because you could just take your modem and router (since you cloned the MAC address in order to get online) to someone else's home and use it. Technically, the ISP's router is still the gateway, but when you use a router, your PC's gateway is the router, and the router's gateway is the ISP's router. Make sense? If not, hopefully this will explain it better:A network gateway joins two networks together. A network gateway can be implemented completely in software, completely in hardware, or as a combination of the two. Since routers are generally used connect 2 seperate networks, for all intents and purposes, a router = gateway. If you are connected to a router in your home (linksys, dlink, whomever), it will act as your gateway to the internet (which is just a collection of networks). Your router's gateway will be the router at your CC. This is the same gateway if you were connected directly to the modem, bypassing the router.

I never understood why cable ISPs tied the MAC address of the first NIC to the account... that question would probably be best answered by the provider.a router acts as a gateway to the internet. If there was was no router (i.e. you were directly connected to the modem), the router at the ISP would be your gateway.

1. I'm not sure on that one... maybe one of the other members can help us out. 2. Behind a router, you can do whatever you want. If you want to statically assign the IPs, you can do that. What they're probably talking about is the router's WAN interface. Where you would set PPOE, or whatever protocol for DSL, one of your choices will be DHCP... that's generally what you set for cable modems. You'll also have to adjust the MAC address in the router to match the PC that initially configured the modem, as cable ties your account to a MAC address

are you a gamer? if so, I'm a huge fan of the D-Link DGL4300. Otherwise, I'd go with a Linksys WRT54G (WRT54GL if you're into using modified firmware). No sense in getting Wireless B devices anymore since G is faster, and nearly as inexpensive Edit: saw you were only looking at wired routers. Why so?

well, there's an easy way to tell if you have DNS issues. 64.233.167.99 put that into you web browser. Google should pop up. there's no "renewal" of DNS, only DHCP. You shouldn't have to flush your DNS cache that often, if ever, if the connection is working. From a command prompt (start > run > cmd) ::::: ipconfig /release once you get an IP of 0.0.0.0, type ::::::ipconfig /renew If you have a good connection (or any connection for that matter), to your router, it should assign an IP. If it does not, try these steps: Log into the router from a machine with a wired connection. Change the wireless SSID to something unique (your name perhaps). Sometimes wireless Access Points can use the same SSIDs, and that can completely mess up a later connection. Make sure no wireless security is enabled (no MAC filtering, no WEP, WDS, etc.) reboot the laptop and try connecting wirelessly again. Make sure you select the SSID you just created. If you get a connection, first try pinging the router (it would be your default gateway), then try surfing the web. If you don't, since you've tried different manufacturers network cards, you can either try an uninstall/reinstall TCP/IP, or format/reinstall of windows.

so do you think it's a continuous file change? If the issue was some random error, or some file got deleted, would those progs tell me?

I'm having a problem w/ one of my employee's PCs, and I've been unable to fix. This is the only workstation where I'm having the problem. We have 4 shared printers, 1 of which is a true network printer, the others are shared from their respective workstations. All 4 are available from this workstation's print dialog (File -> Print), however none of them show up in the printer folder. I've tried stopping and starting the spooler service, no success. I've tried safe mode, nothing. From the printer folder going to file -> server properties gets me nowhere either. Add printer wizard does not start. anyone have any suggestions? Thanks

why not turn off the firewall on the 2nd router (that sits behind the main WAN port entrance), then you only have to forward from the main entrance to its final destination. Wouldn't that be easier?

my vote goes to DD-WRT I love it

deluxe has dual gigabit LAN, which is cool. It could be priced down because they have a large stock of them, and they want to move them. I know AMD is killing off the socket 939, so that could be part of the reason as well

it came bundled as part of SP2, and a quick search on microsoft's site didn't bring up any separate installers. http://www.microsoft.com/windowsxp/sp2/default.mspx You could try downloading and re-installing SP2 and see how far that gets you. it is quite possible that sygate somehow disabled the firewall... so you might want to uninstall it, reboot your PC, and see if it comes back. If not, you could try installing SP2 again, though I wouldn't recommend it.