G
Guest
Hi all....
I configured a Windows 2003 Server machine with "Routing and Remote Access"
but client computers cannot connect to Internet.
Ths is a simplified scenario:
..- Windows Server 2003 configured as Domain Controller, DNS, Active
Directory and DHCP Server. This server has 2 NIC's. One connects to a DSL
modem (let's say NIC A from now on) and the other to a hub (let's say NIC B
from now on).
..- One client computer with Windows 2000 Professional with 1 NIC connected
to the hub.
The configuration I set for each PC is as follows:
1) Server
- Name: WEBSERVER
- Windows 2003 Server, Standard Edition acting as DC, DNS, DHCP Server and
Active Directory
- Software Installed: Exchange server
- NIC A (that connects to the DSL modem) is assigned static IP 10.0.0.1,
automatic DNS and no gateway
- NIC B (that connects to the hub) is assigned static IP 192.168.1.1,
automatic DNS and no gateway.
- Internet connection correctly established. That network connection is set
to have automatic addressing, automatic DNS and no gateway. When I run
IPCONFIG, it shows that IP, gateway and DNS are assigned correctly by my ISP.
- I used the "Routing and Remote Access" wizard to configure the server. I
chose NAT radio button, and then I chose NIC A adapter
- In DNS console, I added my ISP DNS in the forwarder, so that when an
address is not resolved by this server, it will be redirected to my ISP DNS
servers
2) Client computer
- Name: CAROLINA
- Windows 2000 professional
- NIC connected to the hub and automatic IP addressing, automatic DNS and no
gateway.
- When I ping WEBSERVER, it delays some time to resolve the IP but it
finally resolves to the correct one: 192.168.1.1 and PING is successful.
- When I ping an Internet site, for example, www.google.cl, it cannot
resolve the name.
In conclusion, LAN works but it cannot connect to Internet through the server.
What may be wrong with this configuration?
Thanks a lot in advance
Jaime
I configured a Windows 2003 Server machine with "Routing and Remote Access"
but client computers cannot connect to Internet.
Ths is a simplified scenario:
..- Windows Server 2003 configured as Domain Controller, DNS, Active
Directory and DHCP Server. This server has 2 NIC's. One connects to a DSL
modem (let's say NIC A from now on) and the other to a hub (let's say NIC B
from now on).
..- One client computer with Windows 2000 Professional with 1 NIC connected
to the hub.
The configuration I set for each PC is as follows:
1) Server
- Name: WEBSERVER
- Windows 2003 Server, Standard Edition acting as DC, DNS, DHCP Server and
Active Directory
- Software Installed: Exchange server
- NIC A (that connects to the DSL modem) is assigned static IP 10.0.0.1,
automatic DNS and no gateway
- NIC B (that connects to the hub) is assigned static IP 192.168.1.1,
automatic DNS and no gateway.
- Internet connection correctly established. That network connection is set
to have automatic addressing, automatic DNS and no gateway. When I run
IPCONFIG, it shows that IP, gateway and DNS are assigned correctly by my ISP.
- I used the "Routing and Remote Access" wizard to configure the server. I
chose NAT radio button, and then I chose NIC A adapter
- In DNS console, I added my ISP DNS in the forwarder, so that when an
address is not resolved by this server, it will be redirected to my ISP DNS
servers
2) Client computer
- Name: CAROLINA
- Windows 2000 professional
- NIC connected to the hub and automatic IP addressing, automatic DNS and no
gateway.
- When I ping WEBSERVER, it delays some time to resolve the IP but it
finally resolves to the correct one: 192.168.1.1 and PING is successful.
- When I ping an Internet site, for example, www.google.cl, it cannot
resolve the name.
In conclusion, LAN works but it cannot connect to Internet through the server.
What may be wrong with this configuration?
Thanks a lot in advance
Jaime