Solved New Win7 build can't connect to devices past one access point

[ki7xh]

Hi folks,

I just finished rebuilding an old PC, to now run a fresh install of Win7Pro32-SP1. No matter what I do, I can't get it to connect to devices beyond one of two (identical) access points on my LAN.

I have one AP inside my home, which a Win7Home32 netbook and my phone and tablet connect to, and another one outside my home which connects via WiFi to a remote solar-powered camera site about 300 meters away. (At that remote site, there is a TP-Link client router, which connects to an Axis camera, and to a Tycon Power Systems site monitor. All three devices have static IPs set up and the system has been running fine for over six months, with barely a hiccup.)

There are six other PCs here on the network, and three Android devices. All of these (including the Win7Home32 netbook) CAN connect to those three remote devices at the other end of the long-range WiFi link. I can even place an Ubuntu DVD into the drive of the newly built Win7 machine and boot Ubuntu, and it then can see my three remote devices, so I know it's not a hardware issue or unplugged cable. It has got to be something in the LAN adapter settings, or the firewall, or something that's evidently over my head.

When running in Win7Pro32, attempts to connect to the remote devices through that AP just won't go. (I CAN connect to that AP with no trouble - just not to anything beyond it.) Pings to the AP return in less than 1ms. Pings to the devices beyond the AP return "destination host unreachable".

I have no clue what to try next! Thanks in advance for any thoughts you guys might have.

- Darrin

 

[UsernameIssues]

Welcome to the Seven Forums.

On the Win7Home32 netbook that can connect to those three remote devices...
...what does the Network and Sharing Center look like?
(http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html)

...and what does it look like on the problematic computer?

 

[ki7xh]

On the Win7Home32 netbook which can connect, it looks like this...

And on the Win7Pro32 desktop which can NOT get to those remote devices...

 

[ki7xh]

Here's a screenshot of the network map too, which oddly shows the Client Router at the remote site. It knows its MAC address and the IP address. But I can't get to it, or the devices which connect to it. I thought for a second I might have manually configured some proxy settings for Firefox, but it's set to "No Proxy".

 

[UsernameIssues]

I could be wrong - but I do not think that the Ping command uses a proxy.
So Ping should work no matter what proxy setting are in Firefox or IE.

Can you ping the WR743 from the working netbook?
Can you ping the WR743 from the problematic computer?
Have you switched off the W7 firewall as a test?

 

[ki7xh]

I think you're right; ping command isn't falling under Firefox's network settings, so that should be no issue.

I try switching off the W7 firewall on the problematic PC. Made no difference.

Yes, the working netbook can ping the WR743 client router, with 0% loss at an avg. of 45ms.

No, the problematic desktop computer can NOT ping the WR743 client router (even tho' the Network Map knows it's there?!?!). Here's another screenshot, showing just the odd scenario...

(Thanks, BTW, for your help!)

 

[ki7xh]

I solved it... The problem was in the client router in the WiFi-linked remote location. When it DID show up in the Network Map, but I couldn't ping it, I started to think, "What the heck's wrong with that router?"

Did a soft reboot on the router through the its GUI, and it then would provide a login request to the new Win7 machine, BUT then the GUI went down for all machines on my LAN. I took a hike (nice day for it in Wyoming, anyway...) and cycled the power and now it lets the new Win7 box connect to it and the camera and site monitor.

I never even considered rebooting it, since all the other devices were communicating with (and through) it perfectly. Oops. "When in doubt, try rebooting!" is the first thing out my mouth to friends and family. Too bad I couldn't apply my own advice!

Thanks again for taking time to respond.

 

[UsernameIssues]

Glad that you got it working