SBS 2003 Strange Problem



Hi,

I am installing a SBS 2003 in a small environment with 5 client
machines. All 5 machines and the SBS are attached to a switch, along
with a Watchguard Firewall. Internet Access is provided through this
firewall (an ADSL modem is attached).

The problem is as follows:

The clients can get onto the web, but the server cannot. Further to
this, the clients can ping all other clients and the server. The
server cannot ping anything on the network.

I have created an Active Directory domain, and joined the clients to
it. The server is configured with DNS (auto when setting up AD), and I
have since put WINS on it too.

I have set the DNS to have 2 forwarders point to the 2 public DNS
servers given by the ISP. However, as the server cannot seem to route
to the internet, it thinks that the forwarders do not work. The simple
DNS test Passes, but the Recursive does not.

The Firewall is the gateway as I said, and has IP 192.168.3.15. It is
set up with DNS 1 pointing to the server and DNS 2 to the ISP public
DNS.

The server details are set up manually:
IP: 192.168.3.10
SN: 255.255.255.0
GW: 192.168.3.15
DNS 1: 192.168.3.10
WINS: 192.168.3.10

The Clients are all DHCP (from the Watchguard Firewall) with the
following:

IP: 192.168.3.150-250
SN: 255.255.255.0
G/W: 192.168.3.15
DNS 1: 192.168.3.10
DNS 2: ISP DNS
WINS: 192.168.3.10

I have since found that if i try to fix a client IP manually (ie, not
by DHCP) the client can no longer connect to the internet.

It might be worth knowing that I have tried switching the DHCP to the
server, instead of Firewall. The Clients picked up a new IP address
off of the server fine, but could not then get on the internet.

I have tried netdiag /fix and dcdiag on the server. One pointed out
that the default gateway could not be found (which given that I could
not ping it from the server, but could from the clients, didn't really
help much!), and the other that DNS Forwarders were not correct (again,
I know it cannot route to them).

We have an almost idential set up (Firewall, Server 2003 Pro) in
another office, which works fine.

If anyone can suggest anything that may help, I would really appreciate
it. I wonder whether there are a couple of problems here? At first I
thought it was DNS, but now wondering if it is DHCP.

Many thanks,

Andrew

.



Relevant Pages

  • Re: For Microsoft Partners and Customers Who Cant Download or Access
    ... to reconfigure the firewall, but to use a static IP on your client ... and to make sure that the DNS server entries on the client are ... Microsoft for msdn2.microsoft.com. ... use a static IP and set the DNS server addresses to the DNS ...
    (microsoft.public.dotnet.general)
  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: IPTables Blocking Outbound by destination port.
    ... # firewall Firewall startup/shutdown script ... echo "firewall: ... # for each additional server running from 6000 to 6063. ... Clients may access remote POP-3 servers" ...
    (comp.security.firewalls)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: loss of SOME connectivity
    ... I "think" it is DNS. ... Yes, I can ping the router, AND the ISP DNS. ... I cannot connect the inet cable directly to the server because the inet is ... MS firewall not started. ...
    (microsoft.public.windows.server.sbs)

Quantcast