Jeff WCH
Members-
Content count
4 -
Joined
-
Last visited
Never
Everything posted by Jeff WCH
-
It's been a busy week but here are the registry settings I've tried. NameSrvQueryTimeout: Changed value to 10,500, rebooted, no success, changed back to OEM value NameSrvQueryCount: Changed value to 10, rebooted, no success, left value as is TcpMaxConnectAttemps: Changed value to 10, rebooted, no success, left value as is TcpMaxDataRetransmissions: Changed value to 10, rebooted, no success, left value as is TcpMaxConnectRetransmission: Created this key, set value to 10, rebooted, no success, left value as is TcpNumConnections: Created this key, set value to max (16,000,000+), rebooted, no success, left value as is TcpKeepTries: Changed value to 50, rebooted, no success, left value as is TcpKeepCnt: Changed value to 240, rebooted, no success, left value as is EnableFastRouteLookup: Created this key, set value to 1 (on), rebooted, no success, left value as is DefaultTTL: Created this key, set value to 255, rebooted, no success, left value as is I also found a thread that suggested turning on Enable NetBios over TCI\IP so that is turned on. Another thread suggested modifying the LMHOSTS file. But that seemed applicable to a domain based network not the peer to peer we are running. Any thoughts? None of the above changes have fixed the problem. I tried opening a DOS window and pinged the mapped drive, which worked, but when I went back to windows explorer the mapped drive is still listed as disconnected. I’ll keep trying suggestions as long as you have ideas. Jeff
-
WOW, that is an impressive list of settings. Did you come up with that list off the top of your head? It may take a while to research and experiment but I will absolutely keep you posted with findings and results. Thanks for your help. Jeff
-
Thanks for the quick reply. Unfortunately that did not work. One difference between our setups is Techccbcc is running a domain and I’m running a peer to peer workgroup. At this point I have both the original change in GPEDIT.MSC and the change recommended by Techccbcc set to “Enabled”. Going back and rereading the original post by PinkPanther, and the order of things loading. Our (2) XP systems that will not reconnect at logon are both connected to our network through a wireless connection, while the (1) XP system that works fine is hard wired through an Ethernet connection. I reasoned that if the wireless systems took longer to establish a connection, compared to the wired connection, then maybe the attempt to establish a connection to the mapped drive was happening before the wireless setup could establish a connection to the network. So I took out the wireless card and reconnected using a hard wired Ethernet connection on one of the systems. Again, no success. This problem has been frustrating me for several weeks. I’ve searched the Microsoft website and can’t find anything that is relevant. If anyone has any ideas, I’m willing to try just about anything. Jeff
-
I have what appears to be the same problem as Pink Panther. XP clients on a peer to peer network with a mapped drive to a drive on an XP file server. On startup or reboot I get an error message saying "Network drives could not reconnect". If I go to windows explorer and click on the mapped drive (which is labeled as disconnected) the drive and folder on the file server open right up. But if I try to run the software program that needs info from the file server, I get an error message saying "path not found", until I go to windows explorer and click on the mapped drive. Then it works fine. The clients and the file server are all Dell Dimensions with XP Professional SP1. They all run Norton Anti Virus 2003 and Zone Alarm 4.5. Windows firewall is turned off. I've made the change AlecStaar suggested in GPEDIT.MSC with no success. I've shut off NAV and ZA and rebooted with no success. Other possibly useful information. The Windows 98 and Windows 2000 systems work fine. They reconnect automatically after a reboot or shutdown. Also, a third Dell Dimension XP Professional SP1 works fine, so I don't think the problem is at the file server end. Any ideas or suggestions would be appreciated. Jeff