Operating System: W2K Server and Workstation Server: ATLNT2 -> 172.16.2.15 Share:SLXLogging Folder: InFiles Action #1: Open Windows Explorer and enter \\ATLNT2\SLXLogging\Infiles in the address bar and hit enter. Result: Directory contents are displayed [after entering username/password of course] Action #2:Open Windows Explorer and enter \\172.16.2.15\SLXLogging\Infiles in the address bar and hit enter. Result:Error message pop-up stating, "Windows cannot find '\\172.16.2.15\SLXLogging\Infiles'. Check the Spelling and try again, or try searching for the item by clicking the Start button and then clicking Search." Other machines on this LAN can perform Action #1 and #2 without a problem, and I get the same result trying to access any other server or workstation on the LAN. This one computer cannot. [Actually there are two computers that cannot because I managed to recreate the problem on a test machine.] This is not a Browsing or NetBios issue. I would think it would be provided Action #1 Failed and Action #2 succeeded. However as it stands Windows explorer cannot find the server based on it's ip address which leads me to believe that its TCPIP configuration issue. Hell I could be wrong though. Just need some help to figure this one out. Once again it only happens on two machines in this LAN, and it doesn't matter what server/ip address I use.

Can you ping anything on your network? Do you have the right subnet mask? Does it have an IP address?? is it getting an IP from DHCP? if not Manually put one in. Let me know if any of this helped.

Do you have reverse lookup zones setup on DNS. It probably won't make any difference, but it's worth a go.

Is TCP/IP the only protocol installed on ATLNT2? If you run IPCONFIG /ALL on ATLNT2, confirm the IP on it. Also, can you PING the IP of ATLNT2? Perhaps another protocol (such as NetBIOS) is answering when using NetBIOS name in UNC request.