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



Hi - no I'm not able to ping a public ip addr from a workstation.
nslookup does work. I've only used nslookup a couple of times so I'm not
sure what it implies about my issues.

Thanks

In article <epxwF4oOGHA.2236@xxxxxxxxxxxxxxxxxxxx>, not.available@online
says...
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.

.



Relevant Pages

  • Re: NetBios and DNS
    ... I have the PC's configured with the internal DNS server and I have internet ... How I did this NSLookup was like this. ... If you have a zone for your "domain name" and you add the computer records ...
    (microsoft.public.windows.server.dns)
  • Re: Domain Trouble / Windows Server 2k3
    ... run ipconfig /all and note the IP address listed for the DNS server. ... In the box "this connection uses the following items" highlight ... I was able to get the workstation to join. ...
    (microsoft.public.windows.server.general)
  • Re: ***HELP***Joining a "Windows server 2003" domain...WTF!?!?
    ... On the domain controller, run DCDIAG. ... not an external ISP's DNS server. ... Nslookup returns one or more SRV service location records in the following ... controller's Internet Protocol address. ...
    (microsoft.public.windowsxp.general)
  • Re: Win2K Pro does not resolve external hosts unless given static IP
    ... DHCP hands out 10.0.1.1 as ... > make a change in the TCP/IP settings on a workstation ... > ISP's DNS server and then changing it back. ... Check the HOSTS files on the workstations, ...
    (microsoft.public.win2000.dns)
  • Re: DnsApi event id 11151
    ... Set your workstation to use the Active Directory DNS server, usually the DC, ... > settings' then the adapter name, host name, adapterspecific domain suffix, ... > DNS server for the applicable zone that your computer needs to register ...
    (microsoft.public.windows.server.networking)