Cannot ping or access shares on domain controller

I have an urgent issue with a client of mine.  After rebooting their Windows Server 2003 SBS server, no clients can ping or access any shares/print queues on the server.  I can successfully ping the clients from the server but cannot ping the server from any client.  The environment consists of one and only one server.  There's no firewalll/security software installed that I can see is blocing access. Everything was fine until the reboot.  Please help.
tmeehlingAsked:
Who is Participating?
 
Mandeep KhalsaCommented:
Do you have any error messages on the SBS server after reboot? Is the server running out of drive space?
0
 
Mandeep KhalsaCommented:
What is the gateway IP set for both the clients and the server?
0
 
tmeehlingAuthor Commented:
192.168.1.1 - which is their Belkin wireless router
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

 
Mandeep KhalsaCommented:
Can the client ping 192.168.1.1? Can they ping each other? Can they ping the DNS server? Or outside IP address/ domain name?
0
 
tmeehlingAuthor Commented:
Yes, the client can ping 192.168.1.1
No, the client cannot ping the DNS server because it's also the server i'm having problems with.
Client can ping anything outside and browse the internet

Yes, the server can ping 192.168.1.1
Yes, the server can ping the DNS (itself)
Yes, the server can ping outside and browse the internet

0
 
Mandeep KhalsaCommented:
This will sound stupid but did you try to reboot your Belkin router?
0
 
tmeehlingAuthor Commented:
no, but can't hurt.  trying that now
0
 
tmeehlingAuthor Commented:
unfortunately that did not help
0
 
tmeehlingAuthor Commented:
there are no errors .

However, the reason for the reboot was that 1 week ago they were having C: drive space issues.  At the time I deleted some temp files and log files, etc. to get them by for awhile.  In addition, I changed the paging file to use the E: drive instead of the C: drive and set it to "System Managed size".  I told them a reboot was required for that setting to take effect.  A week passed until they rebooted (today), and now this happened.  Related?
0
 
Mandeep KhalsaCommented:
I recently had a case where a server was severly low on space because they had auditing turned on. This caused the free drive space to be in Megs rather than Gigs and the problems caused were explorer.exe getting stuck etc on the client machines. I would recommend you move the location of log files etc to the E drive so that the drive maintains its sanity. Since this is a SBS server move exchange transaction log files, and any other that you can to the new drive.
0
 
tmeehlingAuthor Commented:
Thank you KhalsaComputer.  The fix was to add a pagefile back to the C: drive.  Your comment on the C: drive space issues pointed me in the correct direction.  Thank you very much.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.