Problem with network following standby mode

[Gonzo]

I place my thinkpad T41 in standby mode each night when going home from work. In the morning, I come online and within a minute or so, the network connects, etc.

Lately, the network (and print queues) do not connect to the building network following coming out of standby until I reboot the thinkpad. I do not know of anything that has changed, but this is an annoying thing.

Does anyone know what is causing this and what can be done about it?
Thanks

[hhy2k]

Hi

I do not know what's the reason, but I experience the same with standbuy or hibernate (T40p)

I assume it has something to do with the router and the wireless card... one of these or both hold on to the other and must be reset. I have to reset both, the Thinkpad and the Router (modem) as well. I would appreciate any suggestion to solve this problem as well

Thanks, Erik

[Gonzo]

I resolved it myself by creating a little DOS script that turns off the network and then turns it on again.. basically resettting it.

This appears to work fine. I'm thinking that since this works, the problem [at least for me] may be in the building wiring or network gear.

The script is basically a DOS command set that uses the DOS "NET" command to "STOP" the network and then "START" it back again. I also, do the same to the print spooler, since the network printer seems to be inreachable when this condition occurs.

[geobel]

Not a solution but work around:
Go to control panel/network connections, right click on desired network and choose repair. This usually works for me. You can also choose to display network icon in system tray when connected. Then you just right click network icon and choose repair.

Gosha

[gte204i]

The same thing happens to me. I connect at school, standby, come home, and then I have to do a hard reset on the router to connect.

I'm using access connections and have a WRT54GS router.

Someone mentioned Atheros Client Utility, but I haven't been able to find it for download yet. Anyone know where to get it?

[krosenstein]

Same thing happens to me. All I do is click on the AC icon and reconnect. But you'd think it should reconnect automatically when it comes out of standby the same it connects on boot.

[Gonzo]

OK. Did some web investigation. Found an article on kbalertz.com that discusses this situation. It is article Q317485, "Your Computer Loses IEEE 1394 Network Connectivity When You Resume from Suspend or Hibernate".

The issue with the IEEE 1394 was the context of the article, but it seems to apply to other network hardware as well. Bottom line is that there is a bug with Windows XP where the ARP table does not flush when coming out of Suspend/Hibernate. As a result, the OS thinks that it's ARP table is valid and that the remote location is the problem.

The article says to correct this (for now), open a DOS windows and type:
arp -d *, which clears the XP ARP table.

I tried this and it appears to work. I also installed XP SP2 and it did not help. So until Microsoft fixes XP for this, executing the ARP command is the simplist way to correct things. I built a simple script and launch it from the desktop when I need it.

[hhy2k]

Would you share the script with us? I think many of us would highly appreciate that. Thanks!

[Gonzo]

No prob. It's real simple. Just put the following commands in a file using notepad with a .bat extension, such as: notepad c:\netfix.bat

@echo off
c:
arp -d *


I then created a shortcut on my desktop that called c:\netfix.bat when I clicked on the shortcut desktop icon.

------------------------
Update... I tried this again the next day (when my TB was on standy-by all night) and the arp command did not do the trick. The arp table is actually cleared at that time. So there is still more to this story then arp, but it might be worth experimenting with if you're having trouble.

I continue to investigate.............