Request for help with proper DNS and default gateway settings in a small LAN

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: GordL (gord_at_no.spam.eagleridge-home.com.spamX)
Date: 11/09/04


Date: Mon, 8 Nov 2004 23:09:09 -0500

I run a small test network behind a hardware firewall (Sonicwall SOHO3)
where I test various software and hardware (some of it very obscure) with
the intention of learning what I need to know before rolling anything out in
a mission critical production environment. I recently replaced my 'server'
hardware (due to a motherboard failure) and my Internet proxy/mail server
(Midpoint Gateway) because Midcore Software seems to have disappeared.

Here are the details of my setup. Please understand that I am not
soliciting opinions on my choices of software or hardware. These choices
were made within constraints that were both political and technical and were
highly complex.

Internet connection
Toshiba DOCSIS cable router connected to a
Sonicwall SOHO3 NAT firewall
    WAN port is a DHCP client as required by my ISP but the TCP/IP settings
haven't changed for years.
    LAN facing port is 192.168.1.2. Subnet mask is 255.255.255.252. Default
Gateway is blank and DNS addresses are static but the same as the WAN side.

Dual ported 'server' ( I have been given a lot of advice here.
Unfortunately not much of it has been good.)
    WinXP Pro Running Kerio WinRoute as a proxy
    WAN facing NIC is configured as IP 192.168.1.1 - SNM 255.255.255.252 -
DG 192.168.1.2 DNS same as above (ISP's DNS servers)
    LAN facing NIC is configured as IP 192.168.10.1 - SNM 255.255.255.0 -
DG blank and DNS set to self (192.168.10.1)

Clients
    I have been given a lot of "advice" here as well.
    IP 192.168.10.203 SNM 266.255.255.0 DG 192.168.10.1 DNS 192.168.10.1

At various times I have been told to set up the DNS server address as the
"next hop" yet others have told me to use the ISP's real world DNS servers
even on the clients. I have been told to remove and then later told to
reinstall default gateways on both the server and client machines. My head
hurts. With the sheer number of variables that I am working with it seems
improbable that I will ever stumble on the right settings. Oddly after
various hacking attempts things seem to spontaneously start working and then
just as spontaneously stop. The setup described above actually worked last
night (I was surprised) but would not work the following morning even though
nothing that I know of had changed.

If someone could help me out and provide proper explanations I would be
forever grateful.

Thank you in advance.

Beat regards
GordL



Relevant Pages

  • suspect bug in vge(4)
    ... The high-level view of the problem is that the client seems to stall ... HTTPS server. ... not only printed for TLS/SSL issues but simply also for broken TCP ... To me it sounds like a broken implementation of hardware generated ...
    (freebsd-current)
  • Re: suspect bug in vge(4)
    ... The high-level view of the problem is that the client seems to stall ... HTTPS server. ... To me it sounds like a broken implementation of hardware generated ... Installed FreeBSD 7.1-RELEASE as VM guest, ...
    (freebsd-current)
  • Re: nslookup question?
    ... > If nslookup is unsuccesful, FOR EXAMPLE, showing the ... > how can I force a client to see the Primary DNS as ... > Give me constant errors that RPC server is unavailable. ... for service locations on domain controllers, not for DNS servers. ...
    (microsoft.public.windows.server.dns)
  • Re: suggestions on network storage
    ... If you are using Premium then you have SQL Server and such things are quite possible and quite easy. ... RAID will assist the prevention of loss due to drive failure but that isn't the only point of failure. ... much more to life and if you are serious about managing your server and have hardware limitations ) then get into ntbackup properly! ... But it isn't your place to reject the decision the client makes. ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS Question
    ... I could not get a timeout using ... > they point to the correct ISP DNS servers. ... > server in my client setup, which as I said in my first post solves the ...
    (microsoft.public.windows.server.sbs)