LAN computers cannot connect to Internet through a Windows 2003 Se

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all.....

To simplify the problem I will use only 1 PC in the LAN and the Server that
connects to Internet.

Previously I had configured the server using ICF and ICS and it worked.
Later I tried to use Routing and Remote Access but I had problems so I tried
to get the configuration back to use ICF and ICS again. In that process,
something happened to the DHCP server that it stopped assigning IP addresses
automatically.

This is the scenario:
- Windows 2003 Server that connects to Internet through a DSL modem. This
server has 2 NIC's. One connected to the modem and the other to the LAN (by
mean of a hub). The server is configured as DNS Server and Active Directory.
- One PC with Windows 2000 Professional operating system with 1 NIC
connected to the LAN.

I have seen in DHCP console the following curious items:
- In address leases: 192.168.0.1 BAD_ADDRESS "This address is already in
use". The fact is that no NIC, but one, has assigned IP address 192.168.0.1.
- The server appears to be webserver.mshome.net [192.168.0.1]. Why does it
assign mshome.net? my domain is named CORP
- When I set "Obtain IP address automatically" to the NIC that connects to
the DSL modem, it is assigned 0.0.0.0 (Previously I had this same
configuration and that NIC was assigned a correct private IP address).
- I have always realized that when I configure the PC's in the LAN to have
static IP addesses they cannot connect to Internet through the server. They
could only connect if I set to "automatic addressing", but currently that
"automatic addressing" isn't working.
- If I run "ipconfig /renew" in the client computer, it says that it cannot
connect to DHCP server (but when I PING to the IP address, connection is
correct).

Notice that isn't a hardware or connection problem since if I use static
IP's for the server and for the client PC's, all computers can connect
together but client PC's cannot connect to Internet.
Also Notice that Server connects correctly to internet.

What may be happening?
Thanks a lot in advance

Jaime
 
First, I would use RRAS with NAT. If for some reasons, you need to ics and
icf, check any errors in event view?

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
Networking Solutions, http://www.chicagotech.net/networksolutions.htm
VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
VPN Process and Error Analysis, http://www.chicagotech.net/VPN process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
Jaime Stuardo said:
Hi all.....

To simplify the problem I will use only 1 PC in the LAN and the Server
that
connects to Internet.

Previously I had configured the server using ICF and ICS and it worked.
Later I tried to use Routing and Remote Access but I had problems so I
tried
to get the configuration back to use ICF and ICS again. In that process,
something happened to the DHCP server that it stopped assigning IP
addresses
automatically.

This is the scenario:
- Windows 2003 Server that connects to Internet through a DSL modem. This
server has 2 NIC's. One connected to the modem and the other to the LAN
(by
mean of a hub). The server is configured as DNS Server and Active
Directory.
- One PC with Windows 2000 Professional operating system with 1 NIC
connected to the LAN.

I have seen in DHCP console the following curious items:
- In address leases: 192.168.0.1 BAD_ADDRESS "This address is already in
use". The fact is that no NIC, but one, has assigned IP address
192.168.0.1.
- The server appears to be webserver.mshome.net [192.168.0.1]. Why does it
assign mshome.net? my domain is named CORP
- When I set "Obtain IP address automatically" to the NIC that connects to
the DSL modem, it is assigned 0.0.0.0 (Previously I had this same
configuration and that NIC was assigned a correct private IP address).
- I have always realized that when I configure the PC's in the LAN to have
static IP addesses they cannot connect to Internet through the server.
They
could only connect if I set to "automatic addressing", but currently that
"automatic addressing" isn't working.
- If I run "ipconfig /renew" in the client computer, it says that it
cannot
connect to DHCP server (but when I PING to the IP address, connection is
correct).

Notice that isn't a hardware or connection problem since if I use static
IP's for the server and for the client PC's, all computers can connect
together but client PC's cannot connect to Internet.
Also Notice that Server connects correctly to internet.

What may be happening?
Thanks a lot in advance

Jaime
Click to expand...
 
Back
Top