Cannot access internet on Client networked to SBS 2003?!?

I have a small LAN, running SBS2003, connected via 1 NIC to an ethernet modem, and 1 NIC connects to a switch. At the moment there is only 1 client PC on the LAN (although I have replicated the problem with another PC and a Laptop connected to the LAN via the switch.

Everything works hunky-dory, I have been picking my mails up from Exchange server (sadly enough!) while I have been away. I can even access the server via FTP and VPN.

Okay, so I return from holiday to my office, and the server has been offline, but now it's back online, okay. I try to log into the server, but I can't, check DHCP et al, everything seems fine, still no luck. I repace the swicth, NOW I get an IP address, and can log on. Phew, access to NW resources is fine, I can even get my e-mail from Exchange and send/recieve mails from my client machine using Outlook 2003. But I simply CANNOT connect to the NET via the client? The Firewall is ON on the clients, but footnote says that the machine is getting it'ssettings from the domain.

I have tried disabling the FW in the NW settinsg on the server, but get the 'ipnat.sys is in use etc etc etc' message (addressed on various other threads here. If I stop the FW service in Services, no joy. I looked in RRA, and have disabled the 'basic FW' on the external NIC. No joy. I have set the DNS servers even on the client machine, no joy. I have tried numerous things but am at my wits end. Am I missing something obvoius?

THing that gets me is, I can connect to the server, access NW shared resources (printers etc), I can even pick up my mail via Exchange Server. Sitting on the SERVER, I can access the internet using IE or whateverm but sat at the client machine, NOPE. I even tried looked at Group Policy Manager on the server, to access the Windows FW seetings, but this doesn't appear in the list.

Any ideas peeps? I'm about to cry. I don't know what happened while I was away (apart from a power cut). I have tried

The client machine (PC) has been assigned an IP address correctly


I am running MS SBS2003 SP1 and ave patched it. All machines seem to have had SP2 installed on them as part of the SBSSP1 install process.

Boo! Sorry, reposted on teh Windows Server forum as deemed more relevant. Do I need to close this thread somehow? :confused:

The qucikest thing to do would be to delete the client and then rejoin it to the domain.

Problem is the same for all clients and users on the domain which connect thrrough different computers

Where is DNS coming from? You mention nothing of a router or firewall.

IPCONFIG/ALL INFO. THE ASTERISKED PUT IP IS THE LAST FEW BITS OF OUR STATIC IP (THESE AREN'T ASTERISKED OUT PROPERLY - OBVIOUSLY!!! :rolleyes: )

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\bhollis.fibre>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FIBRE-SERVER
Primary Dns Suffix . . . . . . . : fibre.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : fibre.local

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
Physical Address. . . . . . . . . : 00-0E-0C-6E-78-73
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 83.148.xxx.xxx
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 83.148.xxx.xxx
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 85.189.39.5
Lease Obtained. . . . . . . . . . : 13 September 2006 12:01:56
Lease Expires . . . . . . . . . . : 13 September 2006 12:02:56

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 5751 Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-13-20-3B-71-AB
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 217.79.96.70
217.79.96.71
Primary WINS Server . . . . . . . : 192.168.16.2

C:\Documents and Settings\bhollis.fibre>^A



++++++++++++++++++ DESKTOP CLIENT ON LAN +++++++++++++++++

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\bhollis.fibre>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : bhdell
Primary Dns Suffix . . . . . . . : fibre.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : fibre.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont
roller
Physical Address. . . . . . . . . : 00-13-20-03-CE-E6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.16.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.16.2
DNS Servers . . . . . . . . . . . : 217.79.96.70
217.79.96.71
Primary WINS Server . . . . . . . : 192.168.16.2
Lease Obtained. . . . . . . . . . : 12 September 2006 15:12:15
Lease Expires . . . . . . . . . . : 20 September 2006 15:12:15

Enable NetBIOS over TCP/IP and see if that helps.

Is / are the firewall(s) configured correctly?
May have to uninstall them, configure your system, then reinstall the FW.

You aren't going to believe this, our bloody ISP had changed it's DNS servers and didn't bother to tell us.

It's come back up now.

DNS was set dynamically on the external interface but manually on the internal.

Thankks all for all of your help!

Problem solved.

I can remember one of my first IT classes and the teacher saying, "when all else has failed in your troubleshooting efforts, start looking at DNS". I guess it still holds strue.