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.

The Windows 2003 AD Domain I manage has several Windows XP clients and one Windows 7 RC1 client. Recently, the Windows 7 client has started refusing to access network shares unless the FQDN of the host is provided. Interestingly, DNS resolution using only the hostname works fine. Does anyone know what could be causing this or how to resolve it?

Works Fine

ping hostname

\\hostname.mydomain.internal\MyShare

Doesn't Work

\\hostname
Error: Error code 0x80070035 - The network path was not found.

\\hostname\MyShare
Error: Error code 0x80004005 - Unspecified error

UPDATE

This issue resolved itself about a day after I posted this question. Perhaps it was a time synchronization issue as Moose suggested. Thank you all for your help. If I am ever able to reproduce this problem, I will revisit this question and explore these solutions further.

share|improve this question
    
You can check if it was a time issue by forcing the clock to be off.. if it does break again, it might give you some peace of mind that you might know what the problem is in the future.. and give me some rep points! :) –  Moose Oct 18 '09 at 22:48
    
I tried driving the time out of sync, but that didn't cause the problem. I recently rebuilt that machine, however, using the release version (rather than the RC), so we'll see if it comes back. –  Joseph Sturtevant Oct 22 '09 at 20:09
add comment

7 Answers

Yeah this is a weird issue, and it has been bugging me for weeks. I would love to know the fix for it. I have also noticed that I can browse by IP address.

share|improve this answer
add comment

I've seen this a long time ago, in the Win 2000 days, when the time difference between the client and the server was off by more than 5 minutes. It gives you weird errors that makes you think it's a dns issue when it's really not.

Time Synchronization is highly important to Kerberos.

It may not be the problem but it's easy to check and easy to fix if they are off.

share|improve this answer
add comment

Do you still use wins and netbios? Maybe the netbios over tcp is disabled? When we finally shut wins off we had to go to fqdn, but then again we might be doing something wrong and don't know it.

share|improve this answer
add comment

Did you by chance stop and/or disable the Windows Firewall service in Windows 7 (as opposed to merely disabling the firewall itself)?

Windows 7 encounters all sort of weird network troubles if that service isn't running.

I saw a whole network going completely nuts because someone used a GPO to actually disable the service, instead of only configuring the firewall to be off.

share|improve this answer
add comment

BTW, why are you still on RC1?

The RTM Enterprise evaluation version is freely downloadable: http://technet.microsoft.com/evalcenter/cc442495.aspx.

share|improve this answer
add comment
up vote 0 down vote accepted

I have not been able to reproduce this issue since. Perhaps Microsoft has patched it. If it ever comes back I will update this answer with my solution.

share|improve this answer
add comment

Just had the problem show up on ONE newly loaded Windows 7 machine. Everything comes up fine, works fine, then after an unknown period of time (a day or two), the machine gives the exact symptoms described above. One interesting note - even during these symptoms, I can go to a command prompt and PING the servername just fine.

One more side note: I was able to alleviate the problem by typing in... \servername.domainname.extension - then everything works just fine.

Odd.

share|improve this answer
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.