Cannot connect client to SBS 2003 server

I have a small SBS 2003 Premium installation that runs great. Plenty of
ram, disk and processor. I added three computers without any real problems,
just had to manually point the client's DNS to the server in
Networking...TCP/IP...Properties.

I am now adding a brand new Dell Inspiron 6000 and it will not connect to
save my life. I have read for four hours and tried everything I read to get
it working.

I have:
1) allowed ActiveX
2) added my server to the Trusted zone
3) manually pointed my client to the server for DNS.

My computer can ping the server via ip address, but DNS ping always fails.
Did not have this problem on other PCs. Here is my IPCONFIG /all. Note
that the DNS Suffix Search List is: micske01.fl.comcast.net, that is my ISP,
not my server. Also note that my DNS Servers . . . . . . . . . . . :
192.168.1.11, that's my server hardcoded.

I read that article about DNS forwarding, etc., blew my simple mind. Thanks
for the help in advance.


C:>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : CSS-LAPTOP-5
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : micske01.fl.comcast.net

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network
Connection
Physical Address. . . . . . . . . : 00-12-F0-4D-DB-58

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : micske01.fl.comcast.net
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Cont
roller
Physical Address. . . . . . . . . : 00-11-43-79-3D-BF
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.11
Lease Obtained. . . . . . . . . . : Wednesday, May 18, 2005 3:16:39
PM
Lease Expires . . . . . . . . . . : Thursday, May 19, 2005 3:16:39
PM


.

Relevant Pages

  • Re: No DC in Active Directory
    ... I still show no computers or DCs in AD Computers and Users on Srvr1 and they ... The primary DC points to itself as the DNS. ... The second server ... the first server now shows no DCs in the Active Directory ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client computer internet connection problems
    ... subnet, Default Gateway, correct DNS entry/ies). ... his TCP/IP Configuration settings then he is not going to be able to join ... O*N*L*Y the internal DNS Server IP Address..... ... join the computers to my server domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharing a drive on my computer with others
    ... SBS 2003 needs to manage DNS and really likes to manage DHCP, ... You need to use the wizards on the SBS server to get it all working properly. ... I can't ping any of the computers within the domain. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Replacing Win2000 Domain controllers
    ... Normally you can rename a computer in the domain without any problem, maybe the account did not have the correct rights in AD. ... If you remove it give time for replication and also check that all entries from the DNS management console are deleted and also from the DNS zone properties under the Name server tabs, if it was a DNS server. ... I've tried renaming computers in the domain before and ...
    (microsoft.public.windows.server.migration)
  • Re: Error adding computers to domain
    ... > add Windows 2000 computers to a domain. ... > all because that function isn't necessary on that server. ... While not required by the server, the clients would certainly see a benefit. ... ever use an ISP's DNS server. ...
    (microsoft.public.win2000.advanced_server)
Loading