Hi
I hope someone can , we have just migrated from an NT4 domainto Server
2003, DNS appears to be running fine.
The only problem (which i hope has an easy solution) is we cannot bowse to
our internal firewall (to configure it). The interanl ip address is
192.168.20.0 network but our firewall's internal ip or 192.168.100.6. When we
try and browse to the firewall ip address it tries to resolve it on the
internet and not internal. Is there any record we can put in the DNS server
so the browser will resolve the internal ip address and not go to the
internet.
Hope this makes sense.
Many thanks
Nick

"Nick" <Nick@discussions.microsoft.com> wrote in message
news:7B8AF1D3-9C81-4FF5-9D6A-652BB8EBAEFF@microsoft.com...
> Hi
> I hope someone can , we have just migrated from an NT4 domainto
Server
> 2003, DNS appears to be running fine.
> The only problem (which i hope has an easy solution) is we cannot bowse to
> our internal firewall (to configure it). The interanl ip address is
> 192.168.20.0 network but our firewall's internal ip or 192.168.100.6. When
we
> try and browse to the firewall ip address it tries to resolve it on the
> internet and not internal.

The above makes little sense (as written) since IP addresses
are NOT "resolved" by DNS.

We must assume you are actually using the NAME and expecting
the INTERNAL IP to be its resolution.

This (latter) problem is fixed by unchecking the box on the EXTERNAL
NIC->IP properites->Advanced->DNS tab where it says, register this
connection (and ensuring it IS CHECKED on the internal NIC.)

> Is there any record we can put in the DNS server
> so the browser will resolve the internal ip address and not go to the
> internet.

Just check the DNS NIC settings correctly.

Optionally: You can also give the external NIC an interface specific
name suffix and leave the box checked, e.g., cable.domain.com, or
external.domain.com etc....

> Hope this makes sense.
> Many thanks
> Nick