Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

got IPs from DHCP, but can't connect to Internet

Status
Not open for further replies.

MountainNetworks

IS-IT--Management
Apr 24, 2003
74
Problem is recent. It was working fine.

We are connected to the internet as follows:

DSL-
Watchguard Device .... Linksys 802.11B WAP-
Windows 2000 Server-
Windows XP Workstations
Windows XP Laptops

No proxies, no software firewalls..just the watchguard and that's a hardware device like a linksys.

The workstations are all fine. They are cabled and don't use the wireless at all. No problems.

The laptops:

When connected to the docking station, there are no problems. But remove from docking station and ...

Can get IP addresses, can connect to shared network drives, but can't connect to internet.

I've done all the basic stuff. Ipconfig /renew release, reboot, deleted hardware profiles, removed and readded machines to domain...

Knowing the kind of network card, etc won't help solve the problem. I mention this because I've seen other people with this problem (not on this forum) who have been asked this question.

Has anyone experienced this same thing? What would prevent IE from browsing the internet even if the networking protocols look fine? No ping to the outside world. Not by name or by IP.

Any help would be appreciated. These doctors are effectively down unless they can take their laptops off their docking station and bring them into the exam rooms.
 
Is DHCP enabled on the WAP11?

Disable DHCP and have it obtain from the ethernet side all addressing.

The WAP11 itself should have a static IP, I have no idea from your description what the Watchgaurd DHCP scope might be, but the WAP11 has to be outside of this scope.

Reset the WAP11.

A wireless client should now obtain DHCP services from the Watchgaurd, including the proper Gateway address.

What you are describing is what happens when you have two network segments being created without a common Gateway.

 
This sounds more like a gateway problem to me.

Do ipconfig /all and paste your results in here when you have the machines off the docking stations.

I'm assuming the docking stations are using a wired means to connect to the router?

Anyhow.

Try to ping the router from the laptop. See if that works.

If so, try doing a traceroute to any arbitrary website to see if it goes anywhere.

Also try pinging an IP address on the internet, outside of your network.

Let me know on what happens.
 
Problem Solved. I rebooted the watchguard device and all is well. Turns out the routing tables became corrupted.

Thanks for the help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top