Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

All of the sudden I cannot type " \\my.server.ip.address" in explorer to access shared files/folders like I used to. I could have possibly changed GPO or RDP-TCP settings to screw this up, but I don't remember, and nothing looks odd or different. What is this called and how do I fix it? Host is Windows Server 2003 running terminal services; clients are XP workstations, all on the same domain, and I have no problems connecting via RDP.

share|improve this question
    
GPO and RDP shouldn't have anything to do with it. Do you get any type of error message? –  joeqwerty Sep 24 '10 at 16:03
1  
0% Accept rate on 13 questions? I'll take a chance - can't say anyone else will. –  Matt Sep 24 '10 at 16:33
add comment

2 Answers

up vote 0 down vote accepted

I'm not sure if it's a typo, or the solution to your problem... but:

"\my.server.ip.address"

Should have two slashes, like:

\\my.server.ip.address

share|improve this answer
    
Strange, it had to have 3 to show up double backslashed? –  Daniel Sep 24 '10 at 15:24
    
\ is an escape character in a lot of programming languages, I guess the SO engine tries to make it look pretty or something... either way sorry my answer didn't help! Do you get any error when trying to connect? –  Will Sep 24 '10 at 16:16
add comment

Does it work by name, and just not by IP?

Not sure I'm understanding but if the problem is "none of the XP clients can connect to the 2003 machine share", try restarting the Server Service on your 2k3 box (services.msc). It will say some other things depend on it, that's fine - allow it to restart those as well.

If that doesn't work, and the obvious reboot technique doesn't work either, then try the following which has worked for me in the past on Windows XP (and by extension should work on 2003 as they share a lot of code.)

Go to the network control panel, remove Client For Microsoft Networks by unchecking it. Then re-install it. This re-installs the workstation (server service too?) and will usually jolt the MS core networking (shares, network neighborhood) back into place.

share|improve this answer
    
Yes, only by name. I forgot to check that actually, maybe if I reset my DNS server it will resolve the issue?? –  Daniel Sep 24 '10 at 16:50
    
Ok... Name does work. If you RDP to the IP address you are trying, does that connect to the server you are intending to get to? That would rule out any DNS issue. –  Matt Sep 24 '10 at 17:33
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.