DNS problems - This is driving me crazy

I have one server (sbs 2003 sp1 using 192.168.0.200) with one ethernet
card; one client PC (XP Pro sp2 using 192.168.0.6); and one D-Link
broadband router with a gateway address of 192.168.0.1. Both the server
and the client are physically connected to the router.

I have configured and re-configured DNS on the server numerous times.
Below is the current
ipconfig of my server:

Windows IP Configuration
Host Name . . . . . . . . . . . . : dansbs
Primary Dns Suffix . . . . . . . : dan.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 192.168.0.200

Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
For Complete PC
Management NIC (3C905C-TX) #2
Physical Address. . . . . . . . . : 00-04-76-BB-59-56
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.200
Primary WINS Server . . . . . . . : 192.168.0.200


The server has passed all of the DNS self-tests and can access the
internet just fine. The server CANNOT ping the client.

Below is the current ipconfig of my client:

Windows IP Configuration
Host Name . . . . . . . . . . . . : danxp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dan.local

Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . : dan.local
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-50-2C-06-D0-E5
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.200
DNS Servers . . . . . . . . . . . : 192.168.0.200
Primary WINS Server . . . . . . . : 192.168.0.200

The client can ping the server by IP, name, and fully qualified name.
The client can ping the D-Link box. The client CANNOT access the
internet. The client CANNOT join the domain.

I am puzzled. This should be so easy. I've tried various scenarios. It
seems when I fix one side the other side breaks somewhere else.

Any help would be greatly appeciated.

Thanks in advance.

Dan Maday

.

Relevant Pages

  • Re: Networking issue vs rootkit virus or both
    ... Windows IP Configuration (of local client when giving its own IP) ... Connection-specific DNS Suffix. ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot Connect XP Pro Client to Domain
    ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ... The client uses DHCP and the config is ... As I mentioned the Client can access the Server using RDP and can ping the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cannot join client PC to domain
    ... Server: server1.testdomain.com ... Is it a Vista machine or did you enable IPv6 on a XP client? ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.networking)
  • Re: Cannot Log on to SBS2003 with Win9x clients tho DHCP leases IP
    ... that netbios over TCP/IP is enabled. ... Can you post the ipconfig/all from a client? ... > Please note the ping failure from the server to the client. ... > Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)