One client computer can't access server on domain network

July 21, 2014 at 10:10:19
Specs: Windows 7
The Dell Power Edge T110 II server is running SBS 2011 Essentials. All 8 client computers are running Windows 7 Professional. The Server is connected directly to the ADSL modem. A switch is connected to the modem with all the client computers connecting to the switch. The modem provides the IP address to the server. The client's DNS server is listed as the server's IP address. The server sees and is monitoring all the client computers. All but one client can see and connect to the server. One of the client computers was working fine Friday, but now suddenly can't find the server. I've restarted the client a few times and performed a shutdown and cold boot a few times. I have shut down all the client computers and shut down the switch. then restarted the switch and then restarted the computers. This one Client cannot see or connect to the server. From the server, I can still see this client and can even look at files on this computer. I cannot map a drive to the server from this client. I don't know what else to try.

See More: One client computer cant access server on domain network

Report •


#1
July 21, 2014 at 11:17:35
Okay, for one, is the server providing the DHCP addresses? If it isn't, it's just making things for complex than it should be, at least in my opinion.

Also, make sure that the server has a static IP address. You said that the modem provides the IP address to the server? That also is a bad practice that needs to be corrected, as having all of the clients connecting to a server for DNS that has a dynamic IP can never lead to good things. The one client may not be able to access it because it has an incorrect DNS address for this reason.

And, if you are running an active directory (which I assumed because you said "domain" in the title), it is even more important for the server to have a static address.

You've been helped by a 16 year old.


Report •

#2
July 21, 2014 at 12:33:07
The server has a static address. The server was setup by an outside tech firm and the Owner told them it was fine to leave the modem as the DHCP server since it would save him some money for setup time. "Ipconfig / all" shows the configuration is correct. While running a scan with Malwarebytes (which didn't find any malware), the Client computer finally was able to see and access the server after not being able to all morning.

Report •

#3
July 22, 2014 at 07:33:36
The server was setup by an outside tech firm and the Owner told them it was fine to leave the modem as the DHCP server since it would save him some money for setup time.

Chances are that is a SOHO or mid-grade router then. Modems alone do not have DHCP on them. Running DHCP on it is a good idea because any service you can offload from your DC reduces the load on said DC freeing up system resources for more important work.

One of the client computers was working fine Friday, but now suddenly can't find the server.

Remove it from the domain and then reattach it and see if that doesn't fix the issue with this one client PC.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Related Solutions


Ask Question