Solved Cannot connect to my wireless laptop from my ethernet PC (vice versa)

[Eastwood001]

Greetings,

I have a PC (windows 7) connected to my router (Buffalo AirStation WMBR-HP-GN) via Ethernet cable, while my laptop (Vista) and a 2nd PC (Vista) are using wireless. My Ethernet PC cannot see the laptop or the wireless PC in Network. Both the laptop and wireless PC can see and share with each other. If I use an Ethernet cable for the laptop, I can share with my Ethernet PC.

In short, I can share wireless to wireless, Ethernet to Ethernet, but not Wireless to Ethernet.

Any ideas?

Thanks.

 

[chev65]

Greetings,

I have a PC (windows 7) connected to my router (Buffalo AirStation WMBR-HP-GN) via Ethernet cable, while my laptop (Vista) and a 2nd PC (Vista) are using wireless. My Ethernet PC cannot see the laptop or the wireless PC in Network. Both the laptop and wireless PC can see and share with each other. If I use an Ethernet cable for the laptop, I can share with my Ethernet PC.

In short, I can share wireless to wireless, Ethernet to Ethernet, but not Wireless to Ethernet.

Any ideas?

Thanks.

I would try resetting the router first as it's clearly a problem with the router.

If that doesn't work please post a screen shot of your ipconfig/all from both a wired and wireless machine and I'll see what's up.

 

[Eastwood001]

Tried resetting router, didn't change anything.

Wired machine:

[IMG]http://i.imgur.com/Ijhfw.png[/IMG]

Wireless machine:

[IMG]http://i.imgur.com/XCtWD.jpg[/IMG]

Thanks.

 

[chev65]

Tried resetting router, didn't change anything.

Wired machine:

[IMG]http://i.imgur.com/Ijhfw.png[/IMG]

Wireless machine:

[IMG]http://i.imgur.com/XCtWD.jpg[/IMG]

Thanks.

I believe that I've spotted a problem with the wireless machine, it's a common problem with too many tunnel adaptors. Save the first file below, unzip and click on it, will take a second to run, then reboot your machine.

After that run the second file the same way, let it run until the machine reboots. You might want to update the wireless machines driver after that.

 

[Eastwood001]

Thanks for your help, but other then cleaning out all those tunnel adapters, it doesn't seem to have done much. Still can't share from wired to wireless.

 

[chev65]

Thanks for your help, but other then cleaning out all those tunnel adapters, it doesn't seem to have done much. Still can't share from wired to wireless.

So your haven't set up a Homegroup I presume because it won't work right in a mixed OP system network. So I assume you set up a workgroup using the same workgroup name on all networked machines?

And the Buffalo router is both a wired and wireless router, in the routers set up page for wireless are you using WPA2 security with AES encryption. They are both made to work with wireless N.

If you made any changes to the routers wireless settings be sure and make the same changes to the wireless profiles in Windows.

From what I've read about this router, it's actually one of those modem router combo unit's and the reviews mention updating the firmware to the tomato DD wrt firmware, so at this point I'd have to say the router is the source of the problem if other advice doesn't work.

I looked around and the link below describes the problem you are having with some possible solutions.

One says: If you have a setting like "AP Isolation" or "Client Isolation" make sure that its set to off. Read down to the bottom as the problem looks to be fairly typical but with no clear resolution. Maybe that setting will help.

http://forums.buffalotech.com/t5/Wi...same-subnet-cannot-ping-each-other/td-p/33659

 

[Eastwood001]

It is working now. I'm not really sure what fixed it, but I updated all my drivers using Driver Reviver. Also messed with some router settings.

Thanks for your assistance Chev.

 

[chev65]

It is working now. I'm not really sure what fixed it, but I updated all my drivers using Driver Reviver. Also messed with some router settings.

Thanks for your assistance Chev.

Yes according to that link making changes to the routers settings fixed the problem for some people so I'm glad that worked out.