NAT server problems for weeks Who can help??????????

I have configured a NAT server and clients according the specifications but it is not posible to access the internet from the clients using a brouwser

1-The tracert command issued from the client is working ok. I can get to websites on the internet with tracert.
2-I run a website on the NAT server and a client can access this website on the serve
3-I can ping websites on the internet from the clien

Bu
-Using a brouwser I can not access websites on the internet.

Who can help

On Sun, 6 Jun 2004 12:01:02 -0700, "John Nivard"
<(E-Mail Removed)> wrote:

>I have configured a NAT server and clients according the specifications but it is not posible to access the internet from the clients using a brouwser.
>
>1-The tracert command issued from the client is working ok. I can get to websites on the internet with tracert.
>2-I run a website on the NAT server and a client can access this website on the server
>3-I can ping websites on the internet from the client
>
>But
>-Using a brouwser I can not access websites on the internet.

Define "cannot access" and maybe we can help.

Jeff

Dear Jeff Cochra

Thanks for your help.

The server is connected to the internet using a fixed IP adress . I run on the server the website of the company. I can use a IE brouwser running on the server to connect to the internet and access all websites. I can also connect to the company website on the server.

Using the IE brouwser on the client I can access the companies website running on the server. I can use the computer name S1 or the DN name of this website. But when I try to connect to a website on the internet the brouwser is telling that it can not make a connection to the website. When I issue a tracert from the same client for example to www.kpn.nl it is working o

I you can help many thank

John Nivar

The IP configuration on the server is

Windows 2000 IP Configuratio


Host Name . . . . . . . . . . . . : s
Primary DNS Suffix . . . . . . . : VISIO
Node Type . . . . . . . . . . . . : Broadcas

IP Routing Enabled. . . . . . . . : Ye

WINS Proxy Enabled. . . . . . . . : N

DNS Suffix Search List. . . . . . : VISIO

Ethernet adapter Local


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI For Complete PC Management NIC (3C905C-TX
Physical Address. . . . . . . . . : 00-50-04-42-37-A

DHCP Enabled. . . . . . . . . . . : N

IP Address. . . . . . . . . . . . : 192.168.0.

Subnet Mask . . . . . . . . . . . : 255.255.255.

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.0.

Ethernet adapter internet


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on Motherboar
Physical Address. . . . . . . . . : 00-D0-B7-A9-01-0

DHCP Enabled. . . . . . . . . . . : N

IP Address. . . . . . . . . . . . : 80.242.231.7

Subnet Mask . . . . . . . . . . . : 255.255.255.25

Default Gateway . . . . . . . . . : 80.242.231.7

DNS Servers . . . . . . . . . . . : 80.242.224.
80.242.224.
NetBIOS over Tcpip. . . . . . . . : Disabled

Remove the ISP's DNS servers from the Public Interface. Let the machine use
only the 127.0.0.1 for DNS (since DNS runs on itself). Then add the two
ISP's DNS servers as "forwarders" in the Forwarder's List with in the DNS
Configuration of your DNS service.

All other machines inthe system should use 192.168.0.1 only for DNS.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"John Nivard" <(E-Mail Removed)> wrote in message
news:709A46A1-06E6-4941-A4B0-(E-Mail Removed)...
> The IP configuration on the server is:
>
> Windows 2000 IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : s1
> Primary DNS Suffix . . . . . . . : VISION
> Node Type . . . . . . . . . . . . : Broadcast
>
> IP Routing Enabled. . . . . . . . : Yes
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : VISION
>
> Ethernet adapter Local:
>
>
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI For Complete
PC Management NIC (3C905C-TX)
> Physical Address. . . . . . . . . : 00-50-04-42-37-AE
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 192.168.0.1
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . :
>
> DNS Servers . . . . . . . . . . . : 192.168.0.1
>
> Ethernet adapter internet:
>
>
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
> Physical Address. . . . . . . . . : 00-D0-B7-A9-01-02
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 80.242.231.78
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.252
>
> Default Gateway . . . . . . . . . : 80.242.231.77
>
> DNS Servers . . . . . . . . . . . : 80.242.224.2
> 80.242.224.6
> NetBIOS over Tcpip. . . . . . . . : Disabled

I followed your advise but it is not helping
Windows 2000 IP Configuratio


Host Name . . . . . . . . . . . . : s
Primary DNS Suffix . . . . . . . : VISIO
Node Type . . . . . . . . . . . . : Broadcas

IP Routing Enabled. . . . . . . . : Ye

WINS Proxy Enabled. . . . . . . . : N

DNS Suffix Search List. . . . . . : VISIO

Ethernet adapter Local


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI For Complete PC Management NIC (3C905C-TX
Physical Address. . . . . . . . . : 00-50-04-42-37-A

DHCP Enabled. . . . . . . . . . . : N

IP Address. . . . . . . . . . . . : 192.168.0.

Subnet Mask . . . . . . . . . . . : 255.255.255.

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.0.

Ethernet adapter internet


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on Motherboar
Physical Address. . . . . . . . . : 00-D0-B7-A9-01-0

DHCP Enabled. . . . . . . . . . . : N

IP Address. . . . . . . . . . . . : 80.242.231.7

Subnet Mask . . . . . . . . . . . : 255.255.255.25

Default Gateway . . . . . . . . . : 80.242.231.7

DNS Servers . . . . . . . . . . . : 127.0.0.
NetBIOS over Tcpip. . . . . . . . : Disable

When I use the tracert command at the client it solfs the DN name correctly for exampl
tracert www.kpn.nl is working o

When I type the IP number of a website in the browser at the client than the browser is not connecting to that website!!!!

If we continue to use www.kpn.nl as our sample,...when you trace or ping to
it, what IP# does it resolve to? When I do it here I get 209.144.45.221 and
the site works just fine. Do you get the same IP# by pinging that site?

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"John Nivard" <(E-Mail Removed)> wrote in message
news:BA164686-3A2F-4B4A-A67A-(E-Mail Removed)...
> I followed your advise but it is not helping.
> Windows 2000 IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : s1
> Primary DNS Suffix . . . . . . . : VISION
> Node Type . . . . . . . . . . . . : Broadcast
>
> IP Routing Enabled. . . . . . . . : Yes
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : VISION
>
> Ethernet adapter Local:
>
>
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI For Complete
PC Management NIC (3C905C-TX)
> Physical Address. . . . . . . . . : 00-50-04-42-37-AE
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 192.168.0.1
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . :
>
> DNS Servers . . . . . . . . . . . : 192.168.0.1
>
> Ethernet adapter internet:
>
>
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
> Physical Address. . . . . . . . . : 00-D0-B7-A9-01-02
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 80.242.231.78
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.252
>
> Default Gateway . . . . . . . . . : 80.242.231.77
>
> DNS Servers . . . . . . . . . . . : 127.0.0.1
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> When I use the tracert command at the client it solfs the DN name
correctly for example
> tracert www.kpn.nl is working ok
>
> When I type the IP number of a website in the browser at the client than
the browser is not connecting to that website!!!!!
>
>
>
>
>

No it is different
at the clien
www.kpn.nl = 145.7.192.133 ping is o
www.ibm.com =129.42.21.99 (ping not ok perhaps firwall
www.nist.gov = 129.6.13.23 (ping not ok perhaps firewall
www.klm.com = 171.21.122.77 (ping ok but only one reply

John

"John Nivard" <(E-Mail Removed)> wrote in message
news:CC3875D1-DED8-4920-9B57-(E-Mail Removed)...
> No it is different :
> at the client
> www.kpn.nl = 145.7.192.133 ping is ok
> www.ibm.com =129.42.21.99 (ping not ok perhaps firwall)
> www.nist.gov = 129.6.13.23 (ping not ok perhaps firewall)
> www.klm.com = 171.21.122.77 (ping ok but only one reply)

Sorry, I need to correct, I made an error earlier, here's how mine resolves
www.kpn.nl = 145.7.192.133
www.ibm.com =129.42.21.99
www.nist.gov = 129.6.13.23
www.klm.com = 171.21.122.77

....so they are the same. So let's look elsewhere.

I don't have all the past posts, so I'm a little in the dark. When did the
problem actually start? What was the last thing you did between when things
worked and when they didn't?

1. what does the LAT on the NAT box contain?
2. Is the Company Website on the same box?
3. What IP# is the site "bound" to?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The problem started about 5 weeks ako. I was experimenting with a second server for the website in the network, this because the database of the website a am running is increasing now to 25 giga and is to large to handle on that single server. At a late evening I think I changed the name of the server but I am not shure what I did excatly

When I trace the eventlog I see some errors related to the DNS starting at 30-5-2004
-The DNS proxy agent unable to bind to the ip address 192.168.0.1 This eerror may indicate problems with TCP IP networkin
-The DHCP allocator was unable to check whether the IP 192.168.0.55 is in use on the network for local adress 192.168.0.1. This error indicate a lack of support for adress resolution et

-The DHCP allocator was unable to check whether the IP 192.168.0.120 is in use on the network for local adress 192.168.0.1. This error indicate a lack of support for adress resolution et

The current error is

The DNS proxy agent was unable to resolve a query because no list of name-resolution servers is configured and no interface is configured as the daufault for name resolutio

(this is new and I think telated withe the change in the DN forwareder

Joh