>> The routes look good to me too.
>> Your wired connection has priority over the wireless, so I assume
>> that you unplug your wired connection when testing the wireless.
>> — John>

No, all I’ve done is try to establish an incoming connection by> pinging 10.0.0.204, or trying to connect a VNC client to that> address. I’ve checked the machine’s firewall, and set specific> permissions per adapter, no joy.When a ping packet comes into the wireless address 10.0.0.204, thecomputer tries to send the ping back. According to the routingtable, the wired connection 10.0.0.138 has priorty on outgoingpackets to the 10.0.0.x subnet metric 20 vs. 40, so the return pinggoes out the 10.0.0.138 port. When the return ping arrives at thesending computer with an origin of 10.0.0.138 instead of 10.0.0.204,it discards it because it came from the wrong device and you don’tsee a response.A similar thing will happen on all incoming connections to yourwireless adapter… The return packets will exit on the wired portand confuse the sending device.If you physically unplug the wired connection, then the wirelessconnection will become the priority connection and things may startworking.HTH, John

> John Wunderlich wrote:
>> Philip Herlihy <thiswillbounceb…@you.com> wrote in
>> news:QMrVl.14$Hj6.12@newsfe09.ams2:
>>> It seems very surprising that Ping works this way – this won’t be
>>> the only machine out there with more than one network adapter!

>> It’s not “ping” that works this way, it’s the Network Stack that sits
>> between the NICs and the Applications (e.g. ping) that receive and
>> send packets.  An application will generate a data packet and send it
>> to the network stack which will take care of adding TCP and Ethernet
>> headers, checksums, etc, before directing it to the appropriate NIC to
>> send to the network.

>> You’re right.  Lots of machines have more than one network adapter.
>> The catch in your case is that both adapters connect to the same
>> subnet.  The norm is to have one NIC connecting to one subnet and the
>> other NIC connected to a different, perhaps small, local subnet.  Just
>> Google for “multiple nics same subnet” and you will see the problems
>> that people have.

>> — John

> Quite an education!

> Thanks, John!

> Phil

Most definitely an education.  Once I got the user to disconnect the
Ethernet cable, the connection worked: I can ping the adapter and she
can browse the web – all wireless.
So, one of my tweaks must have fixed things, but since I was operating
remotely via cable, that was obscuring the results.  I guess if I wanted
to try this again I’d set up a (non-persistent) route through the
wireless adapter using “Route Add” for just one target address, and
fiddle around until I could connect to that.

Thank you for your patient and invaluable help.

Best wishes,
Phil (happy now)

> I guess if I wanted to try this again I’d set up a
> (non-persistent) route through the wireless adapter using “Route
> Add” for just one target address, and fiddle around until I could
> connect to that.

“Route Add” should work.  Alternatively, you could also change the
default metric for the wireless interface to have higher priority
(lower metric) than the wired connection — with different side-
effects, of course.

> Thank you for your patient and invaluable help.
> Best wishes,
> Phil (happy now)

Glad to help. Thanks for the feedback.

via Using Wireshark to troubleshoot wireless connections? – comp.os.ms-windows.networking.tcp-ip | Google Groups.

Tags: dhcp, networking, tcp/ip