I have an issue when trying to map to \\server\folder\program.exe or by using the IP of the server in explorer, i get the "\\server\folder\ cannot be found. check your spelling, or try a different path." or "There is no network path". The workstations can see the server but get that error when they try to map to it. The workstation is running Windows 7 Professional and the share is on a file server running Server 2003 with the file server role installed. The XP machines have no issue connecting to the folders and programs. There is a specific program that is stored in the file they need to access. I've verified permissions on the file server share, folder, and program. Any ideas or thoughts would be a huge help! Thanks!

Are the clients and servers on a domain? I've found weird things happen when the network location is not set to Work or detected as Domain network. Questions to help diagnose the issue: Can you map to the server using the IP address? If so, then the issue is likely to do with name resolution (DNS or WINS or both.) Can you browse to the server, simply by typing \\servername (without the share name?) If so, then it points to a problem with the file share. If not, then the problem is not to do with your share, it's to do with your network. Keep us posted :) Ian

Go through this http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/68ffbe2a-09a7-4e29-859c-ca1aaf75dcd1

Its not asking for login credentials I have the same issue when I login to the machine with a domain admin account.

Hi there, as in my post above, what were the results of these tests?Ian

Ok, so now they have access. The prior admin had the server set with an IP automatically provided by NAT, I changed it to static. I couldn't connect by any means: browsing in explorer, using the run with the server name, etc. I changed it back to obtain an IP automatically and it worked. But now the connection is very slow, trying to open a file or folder takes about 5 minutes or wont open at all. The name resolves fine in DNS, and pinging from the server is good also. Pinging the server from the workstation is sproatic, some times its good some times its not. I'm pretty sure I inherited a can of worms. haha!

Now that I changed it back to obtain an IP automatically I can map with IP, or server name. The workstation is on the domain. Like you said I believe its a network issue. I really dont like the face that they are running a .exe from a share folder on a server anyways, but I've got to fix the connectivity issue first before we move on that.

OK. To flush everything on your desktop / laptop, try the following commands in sequence, in a command prompt. These flush all caches and reset the IP stack: ipconfig /flushdns nbtstat -RR nbtstat -R arp -d * netsh winsock reset catalog netsh interface ipv4 reset c:\ipv4reset.log netsh interface ipv6 reset c:\ipv6reset.log You'll need to reboot once done. Also have a look at the network location Windows 7 is picking up your network as. I have strange issues where my network was set to Unknown and similar (in Network and Sharing Center.)Ian

Ok, I'll try that as soon as I get to work and let you know how it works. Thanks for the assist, Sal

Sorry it took me a while to get back to you. Its connecting fine now after running the commands you gave me. Although once you get down about 3 folder levels it slows again.