Just a guess: WINS? The one machine that determines if things connect is the WINS master, and name resolution fails without it.
Troubleshooting: Try connecting via IP instead of name, or FQDN if available. If it does work via these methods, but not by the shortname, I'd bet it is WINS. Solution: Install a WINS server on your 2003 box. Have the DHCP server designate your WINS server. Give it about an hour (Yes, it takes that long sometimes) and your problems should be over. I hope that helps. --Matt ----- Original Message ----- From: Larry Rappaport [mailto:[EMAIL PROTECTED] To: NT System Admin Issues [mailto:[EMAIL PROTECTED] Sent: Wed, 21 May 2008 09:18:43 -0700 Subject: Wierd problem with server > Windows Server 2003. 5 workstations - 4 running Windows XP SP2, one > running Windows 2000 with all service packs. > > If one particular workstation is running (Windows XP sp2), everything is > ok; if that workstation is NOT running, others cannot connect to network > drives (including those on the server) saying that those drives are busy > or not available. All proper services are available and running on the > workstations. Any ideas? > -- > > Larry > rapp at lmr dot com > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
