figger this 1 out. WiFi sees LAN but not outside world

[K8YS]

OK, one laptop, running WinXP Pro, dynamic IP, sees the lan, sees the router, does not see OUTSIDE the router. All the other desktops and laptops as well as a Dell AXIM, can see outside the LAN.

The dead laptop is config for dynamic IP (gets IP address from LAN side DHCP server) also looks for a known good DNS as well as the LAN domain controller as a secondary DNS.

I'm at my wits end on this one and about to pull in another CAT6 to the laptop.

[W7XF]

Try setting the laptop for a STATIC IP (this is what the router will be anyways) and find out what the router's addy will be (USUALLY 192.168.*.*)
and restart the modem (I presume you are DSL or cable.... if you're dialup... YOU'RE ON YOUR OWN :lol: )

Also, make sure your ISP doesn't have router-detection on it (Comcast is famous for this)... this will lock out the internet on other computers... you may have to set up a proxy server if this is the case.

Good luck!

KWH

[K8YS]

Try setting the laptop for a STATIC IP (this is what the router will be anyways) and find out what the router's addy will be (USUALLY 192.168.*.*)
and restart the modem (I presume you are DSL or cable.... if you're dialup... YOU'RE ON YOUR OWN :lol: )

Also, make sure your ISP doesn't have router-detection on it (Comcast is famous for this)... this will lock out the internet on other computers... you may have to set up a proxy server if this is the case.

Good luck!

KWH

yea, I tried that too. The desktops are static, but the mobile devices (2 laptops and an Axim) are dynamic. I set the DHCP pool for 5 devices, with my domain server acting as the DHCP server, and I turned the DHCP server OFF in the brouter.

I did a reboot on all devices, the brouter, the xDSL modem as well as a forced cool boot on the laptap that is suffering a brain fart.

[M0GLO]

Make sure the default route is set for the routers internal address.

[N2RJ]

ipconfig /release

ipconfig /renew

[K8YS]

ipconfig /release

ipconfig /renew

except when the IP address is STATIC.

Now to add to my confusion, I am able to get out of the LAN via the hard wired NIC. The WiFi NIC and the hard wired NIC are config the same...

BUT, the WiFi NIC was able to see all the devices on the LAN, just nothing OUTSIDE the LAN.

[M0GLO]

ipconfig /release

ipconfig /renew

except when the IP address is STATIC.

Now to add to my confusion, I am able to get out of the LAN via the hard wired NIC. The WiFi NIC and the hard wired NIC are config the same...

BUT, the WiFi NIC was able to see all the devices on the LAN, just nothing OUTSIDE the LAN.

Default route OM, default route.

[K8YS]

ipconfig /release

ipconfig /renew

except when the IP address is STATIC.

Now to add to my confusion, I am able to get out of the LAN via the hard wired NIC. The WiFi NIC and the hard wired NIC are config the same...

BUT, the WiFi NIC was able to see all the devices on the LAN, just nothing OUTSIDE the LAN.

Default route OM, default route.

would an ISP filter a MAC?

[M0GLO]

ipconfig /release

ipconfig /renew

except when the IP address is STATIC.

Now to add to my confusion, I am able to get out of the LAN via the hard wired NIC. The WiFi NIC and the hard wired NIC are config the same...

BUT, the WiFi NIC was able to see all the devices on the LAN, just nothing OUTSIDE the LAN.

Default route OM, default route.

would an ISP filter a MAC?

No, but if your routers default route is wrong none of your machines are going to get out.
If it's a missing route on the workstation then that one will not get out.

In both cases you will be able to use the LOCAL network because you are all on the same subnet.

Your default routes tables should have these entries:

For the router: The IP address (NOT the name!) of the ISP router you connect to.
For the workstations: The IP (again NOT the name) of the INTERNAL interface of your internet router.

Both have to be right or it won't work.

[N2NH]

Okay, we had a similar problem here. Seems that with all the Christmas light lately, when the electric company switches in the mains for rush hour we get a surge and it plays havoc with the router/cable modem. Have you done a cold reboot? If you haven't, unplug the power from the back of both the cable modem and the router. Wait 60 seconds and plug in the cable modem. When the cable modem comes up fully, then plug in the router. When that's done, both should be reset. Unless the router lost the configuration that it had all should be well at this point. If, OTOH, the router HAS lost the config, you'll have to access it as per your router's troubleshooting guide or via support.

[K8YS]

I have not idea what was wrong, but all is well now...

Just for grins, I started pinging around, I could resolve the remote name and get the IP address, so the DNS was working. I then remembered that MY SERVER was the first DNS. The laptop was getting resolved from my server.

Then for grins, I ran tracert, resolved the name, started to echo back the route. Passed thru my brouter, to the first router (a Fusenet router) to the next, a Zoomtown router, where it stopped dead. Fuse and Zoomtown are Cincinnati Bell.

I called CBT and explained what was happening... after they said "thats impossible" - it started working about 30 minutes later.

[M0GLO]

I have not idea what was wrong, but all is well now...

Just for grins, I started pinging around, I could resolve the remote name and get the IP address, so the DNS was working. I then remembered that MY SERVER was the first DNS. The laptop was getting resolved from my server.

Then for grins, I ran tracert, resolved the name, started to echo back the route. Passed thru my brouter, to the first router (a Fusenet router) to the next, a Zoomtown router, where it stopped dead. Fuse and Zoomtown are Cincinnati Bell.

I called CBT and explained what was happening... after they said "thats impossible" - it started working about 30 minutes later.

Ahh, yes, the old fixed by magic network!
We had a lot of that network voodoo at a past job site.
Nobody would fess up as to who the wizard was.

[W3WN]

I have not idea what was wrong, but all is well now...

Just for grins, I started pinging around, I could resolve the remote name and get the IP address, so the DNS was working. I then remembered that MY SERVER was the first DNS. The laptop was getting resolved from my server.

Then for grins, I ran tracert, resolved the name, started to echo back the route. Passed thru my brouter, to the first router (a Fusenet router) to the next, a Zoomtown router, where it stopped dead. Fuse and Zoomtown are Cincinnati Bell.

I called CBT and explained what was happening... after they said "thats impossible" - it started working about 30 minutes later.Engineering firm I used to work at originally had Cable & Wireless for our Internet access. About every 6 weeks or so, we'd lose the connection to the outside world -- and since that connection handled the company's email routing, well... I'd be on the horn to Support, although I rarely got the same support group (let alone person) twice. Every time, despite promises to call us, the line would magically come back up on it's own. And every time, no matter who I had talked to, the magic answer always was a "static router table" configuration problem.

Gotta love'em.

[K8YS]

CABLE and WIRELESS! are they still in business?

They had a Cincinnati regional office, I installed the T1 channel bank way back when in the sales office... they were on MCI at the time. I always found that interesting/funny.