Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Server is running Server 2008 R2 Enterprise, Rest are Server 2008 R2 Standard I think its an issue with the credentials that it's using?

This is a backup server that connects to the admin shares of the other servers and backs them up. It has connectivity issues, it can connect to some machines but not others. But this issue is unique to this server.

I can ping the others servers, and if I run the troubleshooter then it says "File and Printer sharing is enabled but the server is not responding to requests"

Attempts to connect to these servers from other machines are always successful.

Any ideas?

EDIT:SOMETIMES if I use the FQDN then it will connect successfully.

share|improve this question
so if you do a \\r2standardserver\ipc$ from the enterprise server does it fail always or is it sporadic? Also do a "dir \\r2standardserver\ipc$" at the command prompt you may see a more discriptive error message. – tony roth Oct 12 '11 at 2:03
If it were an authentication problem (invalid credentials) then it would never connect. If it sometimes connects using the FQDN then it sounds like a name resolution problem to me. I would verify name resolution on this server and your network. – joeqwerty Oct 12 '11 at 3:48
It'd definitely not name resolution, DNS is functioning perfectly, and both hostname and FQDN resolve to the correct IP (ARP also resolves to the correct MAC) – Topherhead Oct 12 '11 at 18:59
@tonyroth I can't access shares at all, if i just do "\\server" It will hangup the same way it would if you put a non-existent machine there. The only difference being that the troubleshooter will recognize there is a system on the other side. Trying to access the share through the command line gives the error "The network path was not found/" Same if you use the FQDN. Windows Network Diagnostics returns "file and print sharing resource([servername] is online but isn't responding to connection attempts." – Topherhead Oct 12 '11 at 19:09
so if you do a \\ipadress\sharename does it work everytime? – tony roth Oct 13 '11 at 5:08
up vote 0 down vote accepted

Well, I don't think I've really found the problem, but I enabled the second NIC on the machine and now its working fine so I don't know what was causing the problem unfortunately but it is functioning now. Presumably something wrong with the other NIC, but everything else was working fine, including connections to some other servers.

share|improve this answer

Your Answer


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.