Member Avatar for slane

I'm new. Hope this is the correct place for my inquiry.

I'm running XPpro on a home network with several computers connecting directly to a router. I'm the only non-mac user and the only one who can't connect to our dsl. We recently got a new modem, a Westell Vistalink 327W. I was fine after installation then all of the sudden; no connection. I can't connect directly or through our wireless. I'm fine on other people's wireless, just not ours.

My automatic IP addresss is a number, I've checked everyone else's and there's are192.168.1 numbers. this is the same for the gateway. When I manually reset mine to match, it doesn't help.

If anyone has any suggestions I would love some help. I've done some pinging, not connected, and I've also checked for firewall problems on my pc.

Thank you in advance. I do a lot of work on-line and this problem is a big one for me.

  • 4 Contributors
  • 6 Replies
  • 188 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by slane

Dani AI

Generated

A short diagnostic summary and next steps based on ’s outcome and the replies from , and .

The key clue is the different subnet: the affected host had a 10.0.1.x lease while the rest of the LAN used 192.168.1.x. That normally means the lease came from a different DHCP server than the home router (an ISP gateway/modem, a second wireless AP, or a local service such as ICS/VPN/virtual-adapter). Manually setting a 192.168.1.x address will work, but the underlying DHCP conflict should be resolved to avoid repeating the problem.

Quick diagnostic commands (run on the XP machine) to identify the source of the lease and confirm routing:

ipconfig /all
ipconfig /release
ipconfig /renew
arp -a
route print

In the ipconfig /all output, note the "DHCP Server" and "Default Gateway" IPs and the NIC MAC. Match those to the router/modem lease table in its admin page. The ARP table and router lease list help identify which physical device issued the 10.x address.

Common causes and how to fix them

  • Two DHCP servers on the same physical network (common when a new modem/router is left in router mode while a separate router is also active). Either disable DHCP on one device or put the modem into bridge mode so only the home router hands out addresses.
  • Incorrect cabling (modem connected to a LAN port instead of the router WAN) can create separate subnets; confirm modem -> router WAN port.
  • XP-specific: check the adapter’s TCP/IP "Alternate Configuration" tab (it can hand out a fallback address).
  • Virtual adapters, VPNs or Internet Connection Sharing can introduce alternate DHCP sources—temporarily disable them to test.

To make the fix permanent: set a DHCP reservation (bind the desired 192.168.1.x to the NIC MAC) on the home router, or ensure the gateway device is the single DHCP server. After changes, power-cycle the modem and router and verify with ipconfig /renew. If the NIC still behaves oddly, then revisiting driver/adapter troubleshooting (as suggested) is warranted.

Recommended Answers

All 6 Replies

Member Avatar for Nick Evan

Well it could be a few things.
-Your lancard is set to a manual IP-adress so it doesn't get an adress from DHCP
-Your card is defect
-Something went wrong with the drivers

You could try removing all your network devices in devicemanager, reboot and then reinstall all the drivers.

Regards Niek

Member Avatar for DimaYasny

first you should try to manually set your IP to your network's numbers. after that, if your hardware is functional, you will be able to ping the router from the inside. after that, if the gateway is set right, and the dns resolving works you'll be able to ping google.com :)

Member Avatar for slane

Thank you so much! I manually set all the numbers and it works. I think the last time I did it I may have had the last 2 numbers of the IP ad wrong.

Any thoughts on why I couldn't automatically obtain these? Not so urgent, but I would like to avoid this in the future.

Thanks again. You made my day.

Member Avatar for DimaYasny

well, you should look into your router's dhcp settings. dhcp should be turned on, and set to give out IPs, gateway and dns addresses

Member Avatar for goldeagle2005

And also make sure that the LAN connection on your computer is set to automatically receive IP via DHCP.

Member Avatar for slane

And also make sure that the LAN connection on your computer is set to automatically receive IP via DHCP.

Yeah, it was. Unless that setting is different than the TCP/IP automatic one. And like I said, I had no problem connecting to any other network. Just this one.

Hmmm.... smart box sometimes confusing...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.