SBS 2003 does not ping router yet serves dhcp and dns to clients which can connect to internet!

Er - is PING the only thing that doesn't work? Can the SBS box access the internet?

Coz some routers are (stupidly) configured NOT to respond to ping.

If you *can't* access the 'net, then check

IPCONFIG - see what other info is in there that may be conflicting
ROUTE PRINT - check that the default route points at the router and that tehre isn't something giving you a second default route.

Does the router have diagnostic tools - can IT ping the server?

no no internet access on the server... forgot to mention that...

router responds to ping, as i can ping it from client machines

ipconfig shows same ip info i mentioned above

i have to check route print will do that tomorrow

router is quite simple i'll see if it can ping tomorrow as well...

Did you run the Configure E-mail and Internet Connection Wizard in the to do list?  If not, you really need to do so.  Click on start, click on server management, click on to do list and then click on the #2 Connect to the Internet which will launch the wizard.  Good luck, Rob.

Rob, yes, I ran it
<quote> i ran IEICW but nothing changes... recreated all DNS and DHCP setups still no no avail <quote>

sorry I wrote IEICW instead of CEICW -- it was a long day

C:\Documents and Settings\Administrator>route print

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 1d 09 fe 41 64 ...... Broadcom NetXtreme Gigabit Ethernet
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1      192.168.1.5      1
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
      192.168.1.0    255.255.255.0      192.168.1.5      192.168.1.5     10
      192.168.1.5  255.255.255.255        127.0.0.1        127.0.0.1     10
    192.168.1.255  255.255.255.255      192.168.1.5      192.168.1.5     10
        224.0.0.0        240.0.0.0      192.168.1.5      192.168.1.5     10
  255.255.255.255  255.255.255.255      192.168.1.5      192.168.1.5      1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None

C:\Documents and Settings\Administrator>

looks normal... i compared it to this laptop which is connected to the same lan as the server and has internet connectivity(the laptop)

ipconfig /all shows:
C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : ompsmsrv
   Primary Dns Suffix  . . . . . . . : OMPSTUDIO.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : OMPSTUDIO.local

Ethernet adapter Server Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-1D-09-FE-41-64
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.5
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.5

C:\Documents and Settings\Administrator>

Sorry I missed that you ran the wizard, should have known what you meant!  This is a bit of a long shot and haven't really spent the time looking at this for you that I should as I have been very busy (tax day.)  But I recall Broadcom having an update to the driver that was needed for some people after a service pack update or windows update.  It is very vague in the back of my mind but figured it was worth mentioning... check for updates to the network adapter as that is worthwhile regardless of my crazy head.  Good luck, Rob.

another thing i've noticed is that local machines connected to the same network are visible on the network. i have updated the broadcom driver but nothing changed. i can ping by hostname so if i do ping accounting  it pings 192.168.1.102 which is correct, and i can see the machiens in net neighborhood...

yet if i try pinging 192.168.1.1 , the att dns, or anoy outside address, even by ip, it times out

The Route and IPConfig outputs all look just right.

The ONLY other thing I can think of...

I installed a network last week and used a set of Level-1 "managable" switches coz they were PowerOverEthernet and I needed that to power up the client's new IP phones. I didn't need the "management" stuff on the switches so I never even looked at it.

I wish I had - coz I realised later that the default IP address on the new switches is 192.168.1.1 - so when I plugged in their new WiFi access point to try to configure it... I was talking to the Switch. And because both devices were tryign to respond it took ages to re-configure the switch to a new IP so it didn't clash with the AP. (Esp as I had TWO switches!)

Could there be ANYTHING at all on your network other than the SBS machine which is configured to 192.168.1.5 ?


Quick way to tell, on a workstation that has TRIED to contact the server recently, type "arp -a" - the MAC address in the table for 192.168.1.5 should be 00-1D-09-FE-41-64 (i.e the same as the IPConfig output above!) - if it's anything else, something else on your network is reporting in as being on 192.168.1.5.


One more test to try - on the SBS box go into Network config, configure the Broadcom card, TCP/IP, Properties, Advanced, and add a *second* IP address to the card (say, 192.168.1.254 255.255.255.0) (do NOT add a second Gateway). Then see if you can access the server via the second address.


Have you run the Security Wizard yet?

Have you tried these tests with the Windows Firewall on the SBS turned off? Have you installed any third party "software firewall" on the SBS?

You might try running

http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx

on the server and seeing if it reacts at ALL when you try to access the server from the 'net.