Automatic IP addressing not working

  • Thread starter Thread starter Tony
  • Start date Start date
T

Tony

I have a small problem that I could use some help with.

I've had a single XP Pro machine hooked up to a router for a long time. A
cable modem is hooked up to the router. That setup has been working
perfectly since I got it up and running. I recently added a wireless router
to the mix, to hook up another XP Pro machine in another room to this small
LAN. Since I know I can't have two DHCP servers on a LAN I kept my older
router as the server and disabled that function from the wireless router (WR
from now on). The WR is hooked up to one of the ports on my old router. I
did this on purpose, as my older router is much more capable in its
configuration and security capabilities, so I wanted the WR behind that.

From my original PC I can ping the net, my old router, and my WR just fine.
My other PC's wireless connection finds the SSID of the WR and connects, but
does not get an IP address with the right octets (192.168.nn) to match how
both routers are set up. Both routers are in the same subnet, BTW. This
second PC is set up to obtain IP address automatically, and all the other
TCP/IP settings that I know are required for that to work. It does get an IP
address, but it starts with 162.254. something or other. I can provide more
info if needed, but I'm wondering if this is enough to point to something
obvious.

BTW, I do not intend to use ICS, as I see no need to with two XP Pro PCs and
both being directly connected to a routed network.
 
What port on "The WR is hooked up to one of the ports on my old router."?

You want to run an ethernet cable from a LAN port on the old router to a LAN
or uplink port on the WR - Not the WR's WAN/Internet port.

What happens if you manually configure the IP, mask, gateway and DNS for the
second PC?

Doug Sherman
MCSE, MCSA, MCP+I, MVP
 
Connection is LAN port to LAN port.

I disconnected this cable from between the two routers and power cycled the
WR. My remote PC still assigned itself one of those 'IP address not found'
IP addresses (DHCP was re-enabled on the WR). I then went into the TCP/IP
settings and assigned an IP address using the correct subnet and pool (along
with mask and gateway). The remote PC did set itself to that address, but I
still could not ping the base address of the WR. I left DNS blank; should I
have set that to the base address of the WR?
 
An update. I brought home my work laptop (also Win XP Pro) and installed the
USB drivers for the USB wireless adapter that I have been trying to use from
my home remote computer. I plugged in the adapter, it detected the network,
and connected just fine. I got a real IP address and could ping the base
address of the WR.
 
Back
Top