sbs2003 can't ping gateway

rcw13 used Ask the Experts™
I am having network access problems and was hoping someone could help me out.  

Our network consists of an sbs 2003 (non-premium) acting as DC for around 25 clients (all XP except two Windows 7) and another server acting as a file server.  The DC also runs DNS and DHCP.  A cable modem supplies Internet access through a Bountiful BWRG-1000 router/gateway.

We had a power outage and after restarting the DC, neither it nor the clients could access the Internet or any of the shared drives on the file server.  None of the clients or the DC can ping the router (the clients and DC give a request timed out error; the other server says "Destination host unreachable.").  None of the clients can ping the DC or other clients, either.

The servers and clients can ping their own IP addresses as well as

The servers and clients access the router through unmanaged switches.  I've changed cat5 cables, changed ports on the switches, and power-cycled the switches and router with no effect.  I've also rebooted the DC several times with no effect.

One wrinkle is that I can connect the DC to one of the LAN ports on the router and get to the Internet (which is how I'm typing this).  I don't think the switches are bad (all the activity lights look normal), but is there an easy way to tell just in case?

Can anyone start me in the right direction?  I've browsed this site and Google for a couple of hours with no success.  Thanks!
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Post an ipconfig /all of your DC. Also have you logged into the router to ensure that it didn't reset it configurations?

Check to make sure that the DNS/DHCP is enabled and has no errors(check the logs).

Post your findings


Here's the ipconfig /all from the DC:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : sbs01
   Primary Dns Suffix  . . . . . . . : ModernBenefitsInc.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : ModernBenefitsInc.local

Ethernet adapter Server Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-14-22-77-53-7B
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . :
   Subnet Mask . . . . . . . . . . . :
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . :

I have checked (and double checked) the router settings and they are the same as before the outage.

Nothing obviously wrong in the DNS log.  But there looks like some random stopping and starting in the DHCP log:

25,09/03/11,15:15:59,0 leases expired and 0 leases deleted,,,,
25,09/03/11,15:15:59,0 leases expired and 0 leases deleted,,,,
24,09/03/11,19:27:34,Database Cleanup Begin,,,,
25,09/03/11,19:27:34,0 leases expired and 0 leases deleted,,,,
25,09/03/11,19:27:34,0 leases expired and 0 leases deleted,,,,
What kind of error(s), if any are you getting in the system event viewer log?
CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Have you tried re-running the (CEICW) The Configure E-mail and Internet Connection Wizard ?


There are some DNS registration/deletion errors (events 5774 and 5775).  Time errors (event 17).  Nothing else out of the usual.


@mikeewalton - yes, I've run the CEICW twice.
Restart these services on the server:

DHCP Service
DNS Service
Netlogon Service

Can you post information I've mentioned above about a workstation? Event viewer log errors, ipconfig /all, nslookup (from server also)

Oh and check the logs after each service.... Let's try to narrow down the your connection problem
*Not a fix, just for troubleshooting*

What happends if you take a workstation and manual set the ip to


D.N.S. (public)

Can it then access internet? Or not?


nslookup from server:
Default Server:  sbs01.modernbenefitsinc.local

nslookup from client:
DNS request timed out
     timeout was 2 seconds
****Can't find server name for address Timed out.
****Default servers are not available
Default server: UnKnown

Windows Ip configuration
Host Name.............: OFFICE4
Primary DNS suffix....: ModernBenefitsInc.local
Node type.............: Hybrid
Ip Routing Enabled....: No
WINS Proxy Enabled....: No
DNS Suffix Search List: ModernBenefitsInc.local

Ethernet adapter Local Area Connection:
Connection Specific DNS suffix: ModernBenefitsInc.local
Description...................: Intel (R) 82562V-2 10/100 Network Connection
Physical Address..............: 00-21-9B-00-17-32
DHCP enabled..................: Yes
Autoconfiguration enabled.....: Yes
IP Address....................:
Subnet Mask...................:
Default Gateway...............:
DHCP Server...................:
DNS Server....................:
Primary WINS Server...........:
Lease obtained................: Saturday, September 3, 2011 8:37:58
Lease expires.................: Sunday, September 11, 2011 8:37:58

Will post results from logs next and try mikeewalton's suggestion on the workstation.


Nothing in the DNS and DHCP logs after restarting those services.


@mikeewalton -- The workstation cannot access the Internet with those settings.

Event Ids in the workstation event viewer include 7 (Kerberos), 5719 (Net Logon), 29 and 14 (W32 TIme) -- several instances of each.  One instance of 8003 (MrxSMB).
Then we need to look at the network layer (i.e. switch, router, etc) instead of anything with the SBS.  Although that has me curious how you got the SBS to access out.
What kind of switches are these? How many?


Netgear ProSafe 24 port and 16 port
I'm not sure of the architecture of your site and how easy this will be, but you currently have the DC plugged into one of the router port in which you are getting access. So we know that's a good port and all. Try taking one of the switches and plugging them into this port, and then the DC into that switch. Test for access. If no, try the other switch.


The DC was connected through the 24 port.  When I bypass that switch and connect the SBS directly through the router, the SBS can access the Internet.  But like I said, both switches appear to be working correctly.
Do you by chance have another switch lying around we can test with.  It appears as either there is an issue with those switches, or something has changed in the gateway and started blocking traffic originating from those switches.


The only other switch I have on hand is a dinky little 4 port D-Link switch.  I can actually get to the Internet using that swith: router-switch-SBS.
just for testing... connect a cable from the 4-port to the main switch and see if any workstation will communicate.


I tried a couple workstations, but neither would communicate.
What are the model #'s on them switches?


JFS524 and FS116
Just from a little research I can see that these appear to be very problematic switches, from power issues, to weird network issues, etc. Since these are pretty much "throw away" switches, I think I would source a couple of locally un-managed switches to get by, then order a couple of good layer 3 managed switches for permanent installation.....As per our testing it definitely appears that we have traced the issue to the switches. Unfortatnately with these being unmanaged switches besides rebooting them, theres not much more we can do with them.

Just to be sure (I expect the same results) you might try moving one of those switches to another port on the router, i.e. one of the ports you are for sure getting access on.

It is also possible that they are not auto negotiating, so you could try a cross over cable, but I'm pretty sure they're just gone.


I'm going to sign off for now and come back to it in the morning.  Looks like I will be going shopping tomorrow to find some new switches.  I will also keep in mind your suggestion of managed swiches.  Thanks for your help!
It really sounds like you have a faulty switch here. So try get a new switch to try with. Start by trying to connect the workstations to each other first. And then try the internet.



Hi guys.  I've installed new switches (temporary, until I can get some good managed switches) and am making progress.  Using a new 24 port switch, the DC and the clients connected to it have access to the Internet and can ping each other.  The workstations can pull IP addresses from the DC.

Part of the problem I eventually discovered is that the other server (file server) had a wonky NIC that worked just enough to fool me that it was OK.  Since I was doing some testing of the network connectivity from that server, it gave a false indication of the state of the network.  I've installed a new NIC and initially it worked great -- it could access the Internet and the workstations could access the shared folders.  After about 15 minutes, however, it can only intermittently ping the gateway and connect to the Internet.  The DC and workstations can sometimes (but not always, say one out of 4 times) ping the file server.

Here's the kicker though -- attempting to patch the other new switch (16 port) into the network throws everything off.  At first I thought maybe it was a bad cable or rogue switch port, but it's not.  With that second switch cabled into the network, neither server can access the gateway reliably and neither can the clients -- the original problem.  When I ping the gateway from the DC maybe 1 or 2 of the packets succeed. From the other server, all result in "Request timed out."  The workstations likewise can't access the Internet when the second switch is involved.

Any ideas on what may be going on with the second switch or the file server?


I should add that the new switches are D-Link, DES-1024D and Dss-16+
a.) What happens with just the 2nd switch uplinked in? Nothing plugged into the 2nd switch.

b.) If fine, what is plugged into that 2nd switch. Start plugging devices in until it throws the network again.

c.) Due to the earlier issue you found with that file server, might want to leave it unplugged until you get the network acting right, then patch it in. Just to be sure it's not causing anymore issues.


a) Everything seems OK with just the 2nd switch uplinked.

b) I think I found the offending cable.  I'm tryng to track down which device it's plugged into.  It's not obvious because everything comes in through a patch panel.

c) Without that particular cable plugged into the 2nd switch, everything seems OK.  I've patched the other server back in, and the workstations can find the shared folders.  The server can also access the Internet.
Excellent, keep me updated on what device you find it to be.


One of the switches was indeed faulty.  I replaced them both (just to be safe) with the result that the network is functioning normally now.  Thanks!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial