Need a little network assistance.

[DTro]

I'm having trouble staying connected to my wireless network via my laptop. Running a cheap Cisco router and Comcast Cable internet. When I'm connected everything works great, but if my PC is idle for several hours, it drops the connection.

This isn't horrible I guess, but the problem is that after that happens it won't reconnect. It hangs at "Identifying". I have to go downstairs and physically power cycle the router.

I basically have to do this every single day. I've tried different "sleep" and "hibernate" modes, and currently using "always on" option. Still no help.

I know the issue is somewhere in the router because I tried powercycling the modem and it didn't help.

The crazy thing is that my wife has the exact same laptop and never has issues.

This is driving me nuts. Please help.

[RuKiddingMe]

Windows Visita?

try this - http://support.microsoft.com/kb/928233

Another thing to try real simple and usually pretty effective, go to control panel --> device manager --> find the wireless card right click uninstall --> reboot your laptop and allow the system to reinstall the wireless card. Next locate your network and try connecting.

[DTro]

Yes, Vista thanks.

I tried clicking the "Fix It" button. We'll see how it goes.

[upnorth]

There are power setting on the NIC to save power. Go in and tell it not to shut down to save power. Go into device Manager-Network Adapters then right click on the wireless adapter and then in power settings uncheck the allow computer to shutdown to save power.

[Shack]

If none of the above fixes the concern, it sounds like maybe your router and or cable connection has a max idle time limit set. The router you can just go into the advanced settings via typing 192.168.1.1 or 192.168.1.0 (could be a simple URL also like www.myrouter.com) in your browser use your user name or password you have created (search router model number & make for default user name and password and change when inside) and access the max idle time on the main settings page, usually basic setup menu and set to 999999 (all 9's) or select a keep alive option. Sounds like something is timing out and that is a killer when doing long downloads or uploads.

You may have to call your local cable company to have them adjust any timeout they have on their end. I do not believe the modem has a time out, but not update and sure about cable.

[DTro]

I think its specific to my laptop because my wife can keep hers idle for days and never has issues.

Thanks for all the suggestions!

[DTro]

I found a "minimum power consumption" and disabled that since it was enabled.

Might as well give that a try too.

[upnorth]

Laptops always have default settings setup to allow for max battery life, not necessarily the most convenient. And not all laptops come back real quick when the NIC disconnects. My new one with "7" works nice, but the older one that had vista had a few quirks.

[pureinsanity]

I swear tons of my posts today have magically disappeared. Darren is it built in wireless or is it a pci card?

[Scott K]

I had the same issue with my linksys router, I had to throw it away, and buy a different router. It would only happen on my laptop too.

I also updated the wireless driver for my laptop at the same time, and havent had the issue since. Not sure which fixed it, the driver update will be free.

[upnorth]

If it was only one PC/laptop? I am going with the drivers curing the issue. Not all wireless adapters and their drivers are created equal. A faulty/funky driver can be as bad a bad piece of hardware.

None of the consumer level router/firewall/APs are going to last forever. Linksys is a big player. I have had one for about 5 years now and yeah it goes through spurts where I need to reboot it frequently, but then it also goes for months without a problem. It is like any other electronic device, have it long enough and it will eventually fail. Don't know too may people with netgear, but I have heard a few folks buying Dlink and thoroughly regretting it.

[Valv]

I swear tons of my posts today have magically disappeared. Darren is it built in wireless or is it a pci card?

Whoops, sorry....

Just kidding, I couldn't resist.

[Valv]

I had the same issue with my linksys router, I had to throw it away, and buy a different router. It would only happen on my laptop too.

I also updated the wireless driver for my laptop at the same time, and havent had the issue since. Not sure which fixed it, the driver update will be free.

I had same issue with my Linksys 160, all of a sudden it will disconnect from modem, then reconnect right away.

I found out it is a common issue after you upgrade the firmware. I was supposed to power it off and reset it instead of just keep using it after the upgrade.

Lately if will disconnect only once in a very while, but it's still annoying, I think it's time to move on to an another brand. I look at it like the Lowrance issues of few years back, time to move on to a better brand, they lost a lot of customers changing their policies.

Now, who's the Humminbird of routers ?

[upnorth]

Could go with a Cisco 2801 Might be a little pricey tho

[pureinsanity]

Whoops, sorry....

Just kidding, I couldn't resist.

[LMITOUT]

I had same issue with my Linksys 160, all of a sudden it will disconnect from modem, then reconnect right away.

I found out it is a common issue after you upgrade the firmware. I was supposed to power it off and reset it instead of just keep using it after the upgrade.

I had a similar problem but the firmware upgrade solved all my issues. In my case the desktop PC (which was connected directly to the router) would lose connection, while my laptop on wi-fi wouldn't drop at all. I believe it's a WRT160 as well. Since the upgrade it's been great and I very rarely reset it.

[upnorth]

Part of the problem can be the ISP too. They make changes to the IP scheme and at times for your router to get new IP info from ISP may need a restart.

[Shack]

Yeah, that is what I was thinking. Maybe a dhcp setting for wireless or a dns server time out but that would not effect just one PC, unless the other pc's are able to fix it on their own. But if his wife is running Vista on the same wireless network and the laptops are the same (would need to be to rule out the network) then I would say it is the laptop and a NIC or realtech issues. I know there is an "ipconfig" command that can be run right after the fact of the failure to give you an idea if it is the network or the pc.

[pureinsanity]

The ipconfig would be for the computer only. I use this all the time to refresh peoples IP's the fast and easy way..

I think Darren has it narrowed down to a PC problem. Same laptops, possibly different wireless cards. He should update the driver and see if that works, or else it is going back.

I still haven't heard if it is built in wireless or PCI?

this weekend I swapped out a wireless router fro my father, his two pc's worked fine, both our phones were able to connect and use it but his wifes computer wouldnt even boot up. she was always dropping connection and getting poor signal. After some research it was hire Wireless NIC. It was/is junk. BAD reviews.... The funny thing was the computer would work fine on the old router but would crash on the new. to fix it we had to uninstall her Wireless NIC, put it into a different slot and reinstall it...

Thanks linksys for your junk wireless NIC

[pureinsanity]

Darren you can also try to reset the winsock services.

Start > Run > cmd > type in "netsh winsock reset" with out the quotes and hit enter. Once done, restart and see if that takes care of it.

[Shack]

Quote:

The ipconfig would be for the computer only. I use this all the time to refresh peoples IP's the fast and easy way

Here you go rookie. Lol.

Quote:

Testing a Network Connection With Ipconfig

If a network having problem, you can use the special command line in Windows Vista to test a TCP/IP installation. The following are three most commonly used commands:

Ipconfig - used to determine if a network configuration has been initialized and if an IP address is assigned. If an IP address and valid subnet mask are returned, the configuration is initialized and there are no duplicates for the IP address. If a subnet mask of 0.0.0.0 is returned, the IP address is a duplicate.

Hostname - used to determine the computer name of the local computer.

Ping - used to query either the local or another computer on the network to see whether it responds.

To test network connection

Click Start, click All Programs, click Accessories, and click Command PromptFrom the Command Prompt window displayed, type: ipconfig and press Enter. The IP address and subnet mask of the current computer should be returned. If this did not happen, there is a problem with the current configuration.

Type: hostname and press Enter.

The computer name of the local computer should be returned.

Type: ping, follow by the name of another computer on your network, and press Enter. You should get four replies from the other computer.

If Ping did not work with a remote computer, try it on the current computer by typing: ping 127.0.0.1 and pressing Enter. Again, you should get four replies, this time from the current computer.

If you didn't get a reply here, you have a problem with either the network setup or the NIC. If you did get a reply here, but not in the above step (on remote computer), then there is a problem either in the other computer or in the cable and devices connecting them.

Close the Command Prompt window.

[Shack]

Quote:

Windows Vista Kills My Network Connection

There is no doubt that Windows Vista delivers the next stage in operating system evolution compared to Windows XP and even to Mac OS X Tiger. One aspect of that evolution and a crucial detail for that matter, is the way Microsoft has understood to provide automatic networking capabilities for the platform. Still when it comes to integrating Windows Vista-based computers into a network, or establishing an Internet connection, the operating system does not always "play well with others".

In this article I will deal with issues that strictly affect Windows Vista. But just to get the idea through I will provide you with two examples of what you won't be able to find an answer for below. I will avoid issues related to system management and maintenance. When dealing with network problems, checking to see that all the hardware is in place and functioning correctly, has to come as the first natural step. Make sure that the network adapter, the cable, the router or switch or hub, etc., all your hardware infrastructure that you rely on for networking is where it should be and doing what it should do. It's simple, and therefore an aspect often overlooked. There is no point in calling Microsoft Support ready to trash Vista and discover that the router is unplugged.

I will also not address problems that Microsoft is offering patches or hotfixes for. You must understand that while some networking problems in Vista are generalized, others are either exceptions, resolved via hotfixes, or through operating system updates. An example of this is the fact that Windows Vista can kill your network, although it had previously functioned perfectly with Windows XP, or slow the network down to a halt when it interacts with outdated routers. Neither you, nor Microsoft can fix an obsolete infrastructure that will clash with the next generation of protocol stack and networking technology in Windows Vista. Theoretically you could take it upon yourself to go and upgrade old routers across your network, but the ISP will probably not welcome such a move on your behalf.

Vista Killed My Network! Help! Everything Was Fine when I Was Working with XP!

Everything might have been indeed just fine when you were running Windows XP, as far as networking is concerned, but now that you have Windows Vista there is no need to think about the past, or to go back to an "expired" version of Windows. Please note the inverted comas, XP is far from expiration when it comes down to support, but it is the obvious conclusion when you contrast it to Windows Vista. So, let's take the following scenarios. You have installed Windows Vista on your computer and you can no longer access the Internet or the network. As I have said above, I will assume that all the right drives have been deployed accordingly, that the hardware infrastructure functions to perfection, that your Internet provider has not cancelled your services etc. Meaning I will assume that Windows Vista is the only one at fault.

Well, fortunately enough for us, Vista comes with a set of new network diagnostics tool built in. And perhaps the most relevant in quickly establishing the connectivity status is the Network Connectivity Status Indicator (NCSI). Remember the old network connection icon in Windows XP that you could add to the system tray? Well, the NCSI, and please feel free to click on the adjacent thumbnail in order to get an accurate idea of what I'm talking about, has replaced the network connection icon in XP. However, unlike in Windows XP, the NCSI icon is able to display four different connectivity access levels.

In the image you will be able to see that the icon delivers four representations in accordance to the aggregated status of all connections: Local and Internet, Local Only, Limited and No Connectivity. The picture will clue you in on how to read the Network Connectivity Status Indicator. The four icons from left to right, above my system tray indicate that the computer is connected both to the Internet and to the local network, or only to the local network, that the machine is not communicating with any other systems or with the Internet, while the last icon with the red "X" symbolizes no connectivity whatsoever, just as if a network cable would be unplugged.

Why is it important to know this? Because it is an integer part of Microsoft's efforts poured into Windows Vista to enable users to correctly assess the nature of a network problem. The first thing that you should do in the eventuality of network problems is right click the Network Connectivity Status Indicator. It will bring up a contextual menu just as you can see in the image on the left. Via this menu users can connect to wireless, dial-up and virtual private network (VPN) networks, open the Network and Sharing center, switch on or off activity animation which is responsible for the NCIS icon blinking when the machine receives packets from the network and turn off notification of new networks. But most importantly you can access the Diagnose and repair the option. This will open Windows Network Diagnostics, a tool designed to analyze network problems and provide a resolve.

A word of advice here for users with computers in environments using proxy servers: NCIS and proxy servers also fail under some circumstances to interact with no issues. This is why Microsoft recommends that users should implement Web Proxy Automatic Discovery (WPAD) proxy detection. Automatic is recommended instead of manual settings due to the fact that the later is synonymous with per user configurations that cannot be used by NCIS by default. However, manual settings along with WinHTTP configuration via command prompt are considered a task that should be reserved for professionals and not home users. But, just in case of a great emergency, you have this resource Automatic Discovery for Firewall and Web Proxy Clients to turn to on Microsoft TechNet.

Down the Rabbit Whole and the Network and Sharing Center

When your network connectivity is inexistent, the Network and Sharing Center should look similar to mine in the image on the left. Vista will generally present you with a Network Error dialog box designed to deliver information related to the nature of the problem but also to provide a shortcut to diagnose and fix it. Vista's Network and Sharing Center will centralize all network connectivity problems and help you resolve them.

The Network and Sharing Center is based on the Network Diagnostics Framework. The NDF is a new feature integrated into Windows Vista with the purpose of guiding users through the process of troubleshooting common networking issues. The best thing about the NDF is that the feature is in a sense context sensitive. What do I mean by this? Well, when confronted with a connectivity error, the NDF will actually isolate to context of the issue and use it as a source for the diagnostic. The difference is between a generalized and a specific analysis, and the Network Diagnostics Framework will ensure not only that it has isolated and identified the specific problem but also that it has automatically repaired it, and will even provide validation of the fix.

And always keep in mind that one of the most important processes in troubleshooting Windows Vista connectivity problems is the good old "Reboot." Once the NDF diagnostic is in place and pointing to your computer, a subset of the network or the whole network considers restarting the affected devices, be it one or several machines or a router or a switch. One thing that Windows Vista has thought is that under some circumstances one reboot is not enough. This does not mean that you should continuously restart your computer and wait for the Network Diagnostics Framework to perform all the heavy "lifting". Set a margin. Mine is about five restarts, followed each time by the automated actions proposed by the Network and Sharing Center. After that, alternative troubleshooting methods have to come in.

In this context, what you have to understand is that if Windows Vista can automatically solve the problem, then it will. The operating system will present multiple scenarios and options to fix issues and users should go through all of them before turning to Microsoft Support. It only requires patience and you don't even have to write a single command line, maybe just a case of manual intervention.

Ping You Bastard, Ping!!! Is My TCP/IP Acting Up?

TCP/IP is the default communications protocol in Windows Vista. The operating system comes with the TCP/IP protocol installed and configured by default, and users don't have much to say in this respect. But Vista does allow for a decent amount of control. How? Well, via the "ping" utility for TCP/IP-based networks, connections problems will be displayed automatically. Pinging your own diagnostic, is a method reserved for the very few exceptions in Windows Vista where the operating system's automatic evaluation of you connectivity fails to highlight an issue. This is of course a clear indication that you need to take matters into your own hands.

Unfortunately this also means that you will have to revert to the command prompt window. Enter "cmd" in the Search Box under the Vista Start menu and then press Ctrl + Shift + Enter in order to launch the tool with administrative privileges. Also, make sure to say "I do" to the UAC prompt... Wonderful!

Now before we get down to the pinging, there is another little command that I want to share with you: "ipconfig". Now in the image on the left I did provide you with a screenshot of what the command returned for my computer. You will notice that I blurred some information; let's just say that I wouldn't want strangers knowing my IP and leave it at that. Alternatively you will be able to enter "ipconfig /?" and access the options which you can use with the command. "ipconfig /all" will return all the information related to your machine including IP configuration, Ethernet adapter, tunnel adapter etc. And as far as pinging is concerned, I have already covered this subject in the past, so now I will just point you in the right direction to the Checking for TCP/IP Connection Problems in Windows Vista.

However, I will say this, there are two ways of repairing a faulty TCP/IP configuration, one is via the Diagnose and Repair option accessible by right clicking the NCSI icon, and the other is through the "ipconfig /renew" command. The latter can be used in the context of a DHCP server. You will know that you are connected to a DHCP server if all the Internet settings in Vista are automated, and you don't have a static IP address. Otherwise "ipconfig /renew" is for IPv4 addresses, "ipconfig /renew6" is for Ipv6 addresses.

I'll Show You My IP if You Show Me Yours...

And I have the feeling that you wouldn't want to share your IP with me... But IP addresses can also generate conflicts because of the automated way in which Dynamic Host Configuration Protocol (DHCP) servers assign them to clients. In addition to the "ipconfig" utility that I mentioned above you can also make your way to the Network and Sharing center and select "Manage network connections" on the left hand side pane. In the window that will open, simply click on the Local Area Connection icon, and in the Local Area Connection status dialog box, at the bottom you will notice three options: Properties, Disable and Diagnose. Hitting the Details button in the middle will deliver the same information (such as IP address, subnet mask, and default gateway) as the "ipconfig" utility, but this is not as much fun, now is it?

Now, under certain circumstances in Windows Vista your IP address will go crazy. The fact of the matter is that you can also diagnose connectivity issues by looking at the IP address. For example, when your computer cannot connect to a network and the DHCP client fails to reach the DHCP server, Windows Vista will not show the dynamic IP address but switch to Automatic Private IP Addressing (APIPA) instead. This means that your IP address will be something like 169.254.a.b. Additionally when the IP address is 0.0.0.0 then you are confronted with an IP conflict because of a duplicate address on a computer connected to the same network or the entire network is not connected.

I Wish They'd Invented a Tool to Check the Network for Me

Well they did... Just in case that you want to see if the technologies across your network support Windows vista, Microsoft is providing users with the Internet Connectivity Evaluation Tool. "The Internet Connectivity Evaluation Tool checks your Internet router to see if it supports certain technologies. You can use this tool on a PC running either the Windows Vista or Windows XP operating system. If you're planning to run Windows Vista, this tool can verify whether your existing Internet router supports advanced features, such as improved download speeds and face-to-face collaboration using Windows Meeting Space. The tool is intended to be run from a home network behind a home Internet (NAT) router. Running this tool from behind a corporate firewall or on operating systems other than those specified above won't produce accurate results," reads the description of the tool.

Your router will be evaluated with a set of tests, and in the end, the Internet Connectivity Evaluation Tool will present its conclusion for the Basic Internet Connectivity Test, Network Address Translator Type, Traffic Congestion Test, TCP High Performance Test, UPnP Support Test and Multiple Simultaneous Connection States Test. You don't even need Windows Vista to perform the tests.

Some of the most common networking issues I came across involved problematic user configuration options. I said it, and it is a detail that bears repeating. Windows Vista has automated connectivity down to the last number in your DHCP IP address. But it needs to be pointed in the right direction. Via the Network and Sharing Center, make sure that you use a private network as a standard. Moreover, turn on Network Discovery to allow Vista to take it from there. Microsoft is also providing two great resources to "Troubleshoot network and Internet connection problems" and to "Troubleshoot problems finding computers on a home network". It's worth a read if you are confronted with such issues.

[pureinsanity]

I spoke with Darren, he has not had any problems since his fix it button. So good to know you are back up and running Dtro.

Shack not trying to burst your bubble here. I will be honest here, I stopped reading what you posted when I saw the words test and ipconfig in the same paragraph. Not trying to be rude either, but here is the link or one of the links you copied and pasted the information from.

Ipconfig just displays all current TCP/IP network configuration values also it can refresh DHCP & DNS settings. Ipconfig just displays the IP address, subnet mask, and default gateway for all adapters.

It doesn't test or troubleshoot anything. It simply just displays what the TCP/IP network configuration values are.

Edit: I forgot to add that with parameters you can release and renew(refresh) the TCP/IP values.

Love,

The rookie that use to do this for a living.

[Shack]

Lol. I put the heading their. I get what you were saying. Just bustin your chops, rookie. ipconfig /test, ipconfig /all was what I was thinking. Maybe another ipconfig command? Sounds like case closed.

[upnorth]

A couple quick tests.

Do the ipconfig but expand that a little to "ipconfig /all" That will give you a little more info.

1st test local network, ping the address of the gateway.

2nd ping the DNS servers, they will most likely be off your network and on the ISP's network. You will get the DNS server with the /all switch.

One thing to look for is if you are getting a 169.254.x.x IP address, that is a standard auto address and means your DHCP server didn't reply with an IP address for your PC.