I'm currently encountering a strange problem in my office, I have a main server running on Windows Small Business Server 2003 and two other servers, a Terminal Server and a File Server both running on Windows Server 2003.
We used to have the terminal server and file server's IP address set to dynamic, but I find it just a better practice to set them to static since they are servers.
Our DHCP server on SBS 2003 is set to exclude the range from 192.168.1.1~10, and SBS2003's local network is on 192.168.1.3
We used to be able to connect to share drives on all the server by typing //fserver/sharename$
After I set our file server's IP address to 192.168.1.5, the UNC path failed to work.
but if I type in the IP of the server directly \\192.168.1.5\sharename it will work just fine.
I first thought it was a DNS issue so I flushed out all the cached DNS record from SBS 2003. Also on one of the client machine I ran nslookup on fserver.domain.lan and it finds the proper IP address for file server, also I tried to ping that IP address as well as its UNC path, both is working just fine.
But when I tried to type the UNC path into explorer window, it just stuck for about 5 minutes and says "Windows cannot find \\fserver\tool$, check the spelling and try again."
I'm just totally puzzled by this issue as the DNS resolve is correct and I just don't see what's the difference between typing in IP directly or using UNC path since they will get resolved to the same thing anyway.