Re: Windows 2003 server, DNS forwarding to internet not working

Have you checked to see whether it is DNS or routing? Can you ping a public
IP from a workstation? What about nslookup from a workstation?

network_out wrote:
Sorry, the server nic was already set to use it's own ip as the pref
dns server. So are the workstations. Still can't browse to the
internet from the workstations.

In article <MPG.1e6aa3286e6543b49899b5@xxxxxxxxxxxxxxxxxxxx>,
network_out <none.none.none> says...
Hi Ace and thanks for responding.

So, for the server nic, do not use the isp dns server address for
preferred dns server? I'll change that (thought Bill meant the ws to
be like that).

The firewall is a smoothwall (as I mentioned but maybe you didn't
know what that was) Smoothwal is an open source project that uses a
stripped down version of FreeBSD running on an old pc with three
nics (lan, internet, and dmz). It has a static ip of 192.168.0.1.

Separately I have a linksys router cable modem but it's actually not
connected...of course it used to be how I connected to the internet.
Maybe I need to use it as a router?

In article <#85#QDnOGHA.1032@xxxxxxxxxxxxxxxxxxxx>,
PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx says...
In news:MPG.1e6a906072afb88d9899b3@xxxxxxxxxxxxxxxxxxxx,
network_out <none.none.none> stated, which I commented on below:
Thanks Bill. As far as I can tell I've done all of that. The ws
report the server ip as the DNS server. Forwarding for dns that
the server cannot handle is pointed to the isp dns server. I'm not
sure if you read all that I wrote, I know it's kind of long, but
something in the details of what I laid out must be wrong.

Actually I read it and you stated:
Win2003 server std, one nic.
IP 192.168.0.10 /24
default gateway 192.168.0.1 (ie firewall)
pref dns server (my isp's dns server address
this win2003 server can browse the internet fine.
dhcp service scope range 192.168.0.100 192.168.0.200

The thing that I see wrong, which you may have missed, which seems
apparent to your response to Bill, is you sated:
"> pref dns server (my isp's dns server address". That tells me
that you are mixing the DNS addresses in IP properties. What Bill
stated is to ONLY use the internal DNS, that's it. As long as the
client is set to use this too, as you stated, that's cool.

For this:
"> default gateway 192.168.0.1 (ie firewall)"
Is that your Linksys NAT router, or whatever name brand? I am
assuming the NAT/router is connected to your ISP (cable or DSL) and
that performs NAT and the internal interface is plugged into the
switch all other machines are plugged into.


.

Relevant Pages

  • Re: Non-domain connection problem
    ... "Gregg Hill" wrote: ... You said that you "hard coded the DNS server to a known DNS on the ... Connect to Internet from external network ...
    (microsoft.public.windows.server.sbs)
  • Re: Added router, lost web site
    ... Did your ISP create a DNS record for your FQDN? ... > really have a direct connection. ... > Internet connection information: ... > Preferred DNS server: someisp DNS server address ...
    (microsoft.public.windows.server.sbs)
  • Re: Unix Bind and Windows DNS with Dynamic update issues!!!
    ... >suggest but it does NOT service internal clients directly. ... still have UNIX BIND to do the rest for host name and internet resolution. ... Windows 2003 DNS will acting as another internal DNS server like UNIX BIND? ...
    (microsoft.public.win2000.dns)
  • Re: sbs 2003 Clients do not have internet access
    ... As I referred in first reply, we do recommend to list any additional DNS on ... the NIC of SBS 2003 and workstation. ... |>able to access the internet. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unix Bind and Windows DNS with Dynamic update issues!!!
    ... >> 2) All internal DNS clients NIC\IP properties must specify SOLELY ... >> we are running UNIX BIND as internal and external DNS server. ... > expose your sensitive internal information on the Internet. ... >> internal clients like Windows, Mac etc are pointing to UNIX BIND server to ...
    (microsoft.public.win2000.dns)
Loading