Losing net connection constantly since new computer added...

Hi all… hope everybody is doing well on this beautiful Saturday… :slight_smile:

I got so tired of trying to get my Linksys Wireless-G broadband router to just get a net connection to my computer in the other room, so I finally ran a 50 foot ethernet cable to it. All was well. Then the second computer sadly died at last. I got a new one. :slight_smile: Unfortunately, the connection immediately started going down constantly but unpredictably (to BOTH computers.) What happens is that it’ll keep insisting it’s connected (“local and internet”) even when it isn’t and nothing is coming up. Turning everything off and then back on again will either fix it or at least cause the message to accurately go to “local only”. On and off again, and then it’ll work.

Sometimes it’ll go quite a while without this happening, but it’s at least once a day. Was there some weird, complicated thing I was supposed to do rather than just plugging the ethernet cable in? The only clue I ever got was one message one time which said “Another computer was detected on the network with the same IP address.” This is what happens when I don’t have a geek around… it’s very sad… anyway, has anyone ever seen anything like this? All advice appreciated!

What are the operating systems of both computers? I ask because Windows 7 has a known wireless bug.

It’s funny you should say this. My first thought was that both of your computers are probably trying to grab the same IP address. Your best bet is probably to turn off DHCP and manually assign them IP addresses. It’s not that difficult and it’ll probably resolve the problem your having. The downside (for the non network savvy) is that you’ll have to do it for any other network equipment your bring in. So, for example, if you want to connect your smart phone to your Wi-Fi, you’ll have to go into the settings and assign it an IP address. Again, not a big deal, just an extra hoop to jump through.

Actually, one other thing, if either of these computers are wireless, go into your router and try changing the channel on it. I’ve had that resolve a lot of problems and it’s much easier then manually assigning IP addresses. If that’s the case it could just mean that one of your neighbors got a new router and it’s interfering with your system.

Go into the command window and type “ipconfig /renew” on both computers

The new one does have Windows 7.

Um… no geeks here… none at all… just an MSW/QMHP… can I have one FedExed to me? They’re so nice to have around the house… (searches unsuccessfully.) I have no idea what you’re talking about. Going into the command window… that wouldn’t cause the computer to explode, would it? I’m always afraid I’ll find that button by accident. :wink:

Command Window
Start>Run> “Cmd” (without the quotes).

It just came back with “the system cannot find the path specified.” :frowning: Is there anywhere to go to learn more about this? I appreciate all the advice so much, but it just doesn’t make any sense without some kind of knowledge base.

What did? When you typed CMD in the Run box or when you typed ipconfig /renew in the command window?

Right after typing ipconfig /renew in the command window.

Try running the command prompt as Administrator if that is not how you are already logged in. Go to Start - Programs - Accessories - then *right-click *on Command Prompt, and choose “Run As…” - and then select Administrator, then try the same command again.

I would note that this won’t solve the intermittent network problem either way. It is just a remedy to get you back online once it happens. Rebooting the computer will have the same effect as renewing your IP address this way, and you have presumably already done that many times throughout this situation.

The problem may be at the router if both of the client computers get taken offline when it happens even if it only started when you added the new computer. If there was only one report of duplicate IP’s on the network among many times this has happened, that probably isn’t relevant to the cause but just a fluke that happened along the way.

I would try resetting the router to the default settings to eliminate some corrupt router setting as the cause. Most routers have a little pinhole at the front, or back, that an unbent paper clip would fit into, with a small button inside that resets the router to the original factory settings. Doing so will reset the administrator name and password to log in to the router to change any additional settings, so make sure you know what those are in advance. They should be given in your router’s documentation online. (usually ‘administrator’ and 'password", but YMMV)

Okay, first off all, just to make sure you’re in the right place, the command window is a black bow that says something along the lines of c:[something]> correct?
It should look something like this.

(I apologize if I’m dumbing this down to far, I just want to make sure we’re all on the same page here)
Assuming that’s where you are, lets just try typing ipconfig to see what happens. This will eliminate something wonky happening with the switch.


The “DOS Prompt,” “Command Prompt,” “Command Window,” “Command Line,” “Command Line Interface(CLI),” “Shell,” “Terminal,” “Text User Interface(TUI),” and “Black-box thing” are essentially technical terms describing the same thing.


I have had several linksys routers go TU. The WiFi goes first, then eventually they constantly reset. I was able to fix one by re-capping the power supply. (switching regulator inside router, not the wall wart) So if the power supply is weak, it may have enough to drive one UTP connection, but not enough for two.

Ditto. I’ve been switching over to Netgear for my routers and switches.

However, I’m not convinced this one is dead since it started acting wonky just after a new computer was brought into the mix. I’d try some other (free) options before I’d plunk down $50-$80 for a new one.

Duckster, what’s the known wireless bug? We recently diagnosed a difference in the way Windows 7 resolves DHCP requests compared to Windows XP, but in our case the problem was firmly with certain Cisco features we had enabled.

Well, after trying various options, I finally gave up on that wireless router. I refuse to keep messing with that thing anymore… An old-school $10 switch is coming from Amazon tomorrow, and there will be (free) Ethernet cables all over the floor! :slight_smile:

Then you will definitely need to hard set IP addresses as a switch cannot assign them automatically. It lacks DHCP functionality.

You do realize that if you replace the router with a switch you must manually assign IP addresses…right?

Come to think of it, having only one unmanaged switch in the mix won’t work. You have to have some way to direct the traffic to the modem. Even if you don’t use the DHCP feature of a router, you still have to have a router in the mix somewhere. Switches are typically used to give you the ability to add more computers or other devices. For example, I have a switch in my entertainment center that my TiVo, TV, DVD Player and Receiver connect to and then I only have to run one wire back to the router in the basement. Much more convenient then running 4 wires back to the router.

I’m assuming the OP must mean a router with a switch - basically what they have now except without wireless. They probably won’t be able to get connected to their ISP using just a switch before we even start talking about assigning internal IP addresses.

The wireless probably wasn’t the problem since the it also happened on a wired connection to the router, but a new router may coincidentally solve whatever the problem was.

Hopefully, the instructions will be in the box. Yes, I’m pretty sure it’s a router with a switch… actually, I’ve just been plugging the cable right from the cable box into my laptop for the past couple of days, and it’s so nice and simple and works so well without a single problem-- if I didn’t have another computer to hook up, I would just keep doing that. :slight_smile: