Problems while both interfaces wired and wireless available on computer

You should set different subnet for the interfaces.

example:
Wired 192.168.0.x 255.255.255.0
Wireless 192.168.1.x 255.255.255.0

Gateway only one default gateway is permitted
example: 192.168.0.254 (will use wired interface to exit your lan)

You can set a different gateway for each interface:

C:\>ipconfig/all

Windows IP Configuration
        Host Name . . . . . . . . . . . . : IXP8200
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : Yes
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local A-G Wireless Connection:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Atheros AR5006X Wireless Network Adapter
        Physical Address. . . . . . . . . : 00-16-E3-88-16-23
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.228.104
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : fe80::216:e3ff:fe88:1623%4
        Default Gateway . . . . . . . . . : 192.168.228.10
        DHCP Server . . . . . . . . . . . : 192.168.228.10
        DNS Servers . . . . . . . . . . . : 192.168.228.10
                                            fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1
        Lease Obtained. . . . . . . . . . : Thursday, 17 July, 2008 00:39:31
        Lease Expires . . . . . . . . . . : Monday, 18 January, 2038 23:14:07

Ethernet adapter Local Ethernet Connection:
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet Controller
        Physical Address. . . . . . . . . : 00-08-74-E0-D6-EF
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.50
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : fe80::208:74ff:fee0:d6ef%5
        Default Gateway . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.1.1
                                            fec0:0:0:ffff::1%2
                                            fec0:0:0:ffff::2%2
                                            fec0:0:0:ffff::3%2

Multi default gateways solution will give a lot of problems in packet routing.
You should have only one DEFAULT gateway.
You can add more gateways but only for specific adderesses / networks with cmd ROUTE ADD

Above no one soulution workded for me. Let me give more details here.  The source machine which is placing request via SYN for connection on Wireless interface is getting the response packate SYN ACK with the wireless IP but still it is discarding the packate and sending RST packates. I think here may be MAC address is the problem. I could see that the response packate contains Wireless IP address which comes through wired interface but this packate dont have wireless MAC address. it contains wired MAC address. I am not sure may be this is problem. Following is the my network details.

C:\>ipconfig/all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : agapanthus
        Primary Dns Suffix  . . . . . . . : hyd.deshaw.com
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : hyd.deshaw.com
                                            hyd.deshaw.com
                                            hyd.deshaw.com
                                            deshaw.com

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : hyd.deshaw.com
        Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
        Physical Address. . . . . . . . . : 00-1C-23-3B-32-21
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 149.77.172.132
        Subnet Mask . . . . . . . . . . . : 255.255.252.0
        Default Gateway . . . . . . . . . : 149.77.172.10
        DHCP Server . . . . . . . . . . . : 149.77.160.1
        DNS Servers . . . . . . . . . . . : 149.77.160.1
                                            149.77.160.2
        Primary WINS Server . . . . . . . : 149.77.160.31
        Secondary WINS Server . . . . . . : 149.77.160.35
        Lease Obtained. . . . . . . . . . : Friday, July 18, 2008 12:08:37 PM
        Lease Expires . . . . . . . . . . : Saturday, July 19, 2008 12:08:37 AM

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . : hyd.deshaw.com
        Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
k Connection
        Physical Address. . . . . . . . . : 00-1F-3C-32-E3-8E
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 149.77.163.239
        Subnet Mask . . . . . . . . . . . : 255.255.255.128
        Default Gateway . . . . . . . . . : 149.77.163.129
        DHCP Server . . . . . . . . . . . : 149.77.160.1
        DNS Servers . . . . . . . . . . . : 149.77.160.1
                                                       149.77.160.2
        Primary WINS Server . . . . . . . : 149.77.160.31
        Secondary WINS Server . . . . . . : 149.77.160.35
        Lease Obtained. . . . . . . . . . : Friday, July 18, 2008 12:35:31 PM
        Lease Expires . . . . . . . . . . : Saturday, July 19, 2008 12:35:31 AM

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 1c 23 3b 32 21 ...... Broadcom NetXtreme Gigabit Ethernet - Determinis
tic Network Enhancer Miniport
0x3 ...00 1f 3c 32 e3 8e ...... Intel(R) PRO/Wireless 3945ABG Network Connection
 - Deterministic Network Enhancer Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   149.77.163.129  149.77.163.239       1
          0.0.0.0          0.0.0.0    149.77.172.10  149.77.172.132       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
   149.77.163.128  255.255.255.128   149.77.163.239  149.77.163.239       25
   149.77.163.239  255.255.255.255        127.0.0.1       127.0.0.1       25
     149.77.172.0    255.255.252.0   149.77.172.132  149.77.172.132       10
   149.77.172.132  255.255.255.255        127.0.0.1       127.0.0.1       10
   149.77.255.255  255.255.255.255   149.77.163.239  149.77.163.239       25
   149.77.255.255  255.255.255.255   149.77.172.132  149.77.172.132       10
        224.0.0.0        240.0.0.0   149.77.163.239  149.77.163.239       25
        224.0.0.0        240.0.0.0   149.77.172.132  149.77.172.132       10
  255.255.255.255  255.255.255.255   149.77.163.239  149.77.163.239       1
  255.255.255.255  255.255.255.255   149.77.172.132  149.77.172.132       1
Default Gateway:     149.77.172.10
===========================================================================
Persistent Routes:
  None

Some more details I could pint wireless IP successfuly but not able to access C: drive through \\WirelessIP\C$.. Everything is working fine through wired IP address because it replying on wired interface only. For replying source machine not using wireless IP interface at any point.

Thanks.

sorry for typo in previous update:

details I could **ping** wireless IP....

Thanks.

Now you are using Internet public addresses and not Lan addresses. What kind of config are you tryng to run ?

As i said before:
The Default gateway MUST be present ONLY in one adapter.
If you set the default gateway on every interfece yoy'll have troubles.

Try to disable alternatively the lan and the wireless interface ans see if they function separately.

> but not able to access C: drive through \\WirelessIP\C$
 
Not able to access the \\149.77.163.239\C$ share from 'where'?
From another computer on that same 149.77.163.128 /25 subnet?

> What kind of config are you tryng to run ?
 
It appears D.E.Shaw & Co. has the entire 149.77.0.0 /16 block.
See http://ws.arin.net/whois

Yes but is a strange config, isn't it ?

>>Not able to access the \\149.77.163.239\C$ share from 'where'?
Yes from 149.77.175.220 (this is wired interface IP). But i could access \\149.77.171.132\C$.

Thanks,

>>As i said before:
>>The Default gateway MUST be present ONLY in one adapter.
>>If you set the default gateway on every interfece yoy'll have troubles.
>>Try to disable alternatively the lan and the wireless interface ans see if they function separately.


I did following tests and got the packets information using wireshark.

If I disable wireless interface then there is no use and behavior will be same. Now I have disabled wired interface as below:

C:\route delete 0.0.0.0 mask 0.0.0.0 149.77.172.10
C:\ipconfig /flushdns
C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 1c 23 3b 32 21 ...... Broadcom NetXtreme Gigabit Ethernet - Determinis
tic Network Enhancer Miniport
0x3 ...00 1f 3c 32 e3 8e ...... Intel(R) PRO/Wireless 3945ABG Network Connection
 - Deterministic Network Enhancer Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   149.77.163.129  149.77.163.239       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
   149.77.163.128  255.255.255.128   149.77.163.239  149.77.163.239       25
   149.77.163.239  255.255.255.255        127.0.0.1       127.0.0.1       25
     149.77.172.0    255.255.252.0   149.77.172.132  149.77.172.132       10
   149.77.172.132  255.255.255.255        127.0.0.1       127.0.0.1       10
   149.77.255.255  255.255.255.255   149.77.163.239  149.77.163.239       25
   149.77.255.255  255.255.255.255   149.77.172.132  149.77.172.132       10
        224.0.0.0        240.0.0.0   149.77.163.239  149.77.163.239       25
        224.0.0.0        240.0.0.0   149.77.172.132  149.77.172.132       10
  255.255.255.255  255.255.255.255   149.77.163.239  149.77.163.239       1
  255.255.255.255  255.255.255.255   149.77.172.132  149.77.172.132       1
Default Gateway:     149.77.172.10
===========================================================================
Persistent Routes: None

Now only wireless interface is there on destination machine. Now from source machine(149.77.175.220), if I tried to do \\149.77.163.239\C$ then also I am getting "Network path not found"(Please refer the attached snapshots of both the machines packets trace).But still \\149.77.172.132\C$ works fine. This will work because through wired interface communication router will not come into the picture as both the machines(while looking as wired interface) are in same network so they can communicate via access switch itself.

Aha...I got the exact problem now. Please see below:

When I try to do \\149.77.163.239\C$(wireless IP - this is destination machine) from 149.77.175.220(wired IP - this is Source machine) the request goes via local router to 149.77.163.239 because source machine will understand that wireless IP 149.77.163.239  is not in my network. When destination 149.77.163.239 machine got the request from 149.77.175.220, it will understand that this machine is in my network(because of wired 149.77.172.132 IP) and it will reply via access switch. Ahaa I think now I am right. What I want even though destination machine understand that 149.77.175.220 is in my network, it should sent a reply packet via the interface from where packets arrived. If this is done then there will not be any problem.
   
Could you suggest to make this possible so that destination machine should reply from the interface from where request packate arrieved.

Thanks,

Please also note that if i remove wired interface cable then wireless IP is starts working without any problems. but both are not wokring together.

Thanks,
Paresh

> Yes from 149.77.175.220 (this is wired interface IP). But i could access \\149.77.171.132\C$.
 
Could you show us a lightweight/limited 'map' of the layout (do youhave Visio, or the OpenOffice Draw program?), or a more-complete description of exactly what you're trying to do, please?
I think you've just about talked yourself through it, but I'd like to make sure we understand too. ;-)
There was no trace attached, btw.

ok from the jump ms os's will not allow for this kind of config to work.  It goes for  the highest priority.  now you can change the priority list and place wireless highest on the food chain as you will but that means it will look to that first for a connection and then when it doesnt have it got to other means.  It sounds like what it is doing right now is starting a connection with the wireless and then its like OH NO wired is higher and then trying to switch over which interupts the tcp connect cycle thuse causes all these errors.

Sorry forgot to attached Traces file...I have also attached visio diagram of our networkd. The IP addresses given is not a true but just for an example.

Thanks
packates-on-destination-wired-In.JPG
packates-on-destination-wireless.JPG
packates-on-source-machine-conta.JPG
network.JPG

>>Could you show us a lightweight/limited 'map' of the layout (do youhave Visio, or the OpenOffice >>Draw program?), or a more-complete description of exactly what you're trying to do, please?
You can see network.jpg in previous reply for our network architecture and I think following paragraphs tells in detailed what i trying to do. Please let me know if you are looking for any specific details.

Now only wireless interface is there on destination machine. Now from source machine(149.77.175.220), if I tried to do \\149.77.163.239\C$ then also I am getting "Network path not found"(Please refer the attached snapshots of both the machines packets trace).But still \\149.77.172.132\C$ works fine. This will work because through wired interface communication router will not come into the picture as both the machines(while looking as wired interface) are in same network so they can communicate via access switch itself.

Aha...I got the exact problem now. Please see below:

When I try to do \\149.77.163.239\C$(wireless IP - this is destination machine) from 149.77.175.220(wired IP - this is Source machine) the request goes via local router to 149.77.163.239 because source machine will understand that wireless IP 149.77.163.239  is not in my network. When destination 149.77.163.239 machine got the request from 149.77.175.220, it will understand that this machine is in my network(because of wired 149.77.172.132 IP) and it will reply via access switch. Ahaa I think now I am right. What I want even though destination machine understand that 149.77.175.220 is in my network, it should sent a reply packet via the interface from where packets arrived. If this is done then there will not be any problem.
   
Could you suggest to make this possible so that destination machine should reply from the interface from where request packate arrieved.

Thanks,

I think this problem is nothing to do with an our network architecture but its related to packate forwarding rules.** If machine replies on the interface from where packate arrieves then there will not be any problem.** Could any one please let me know if this is happening in Microsoft TCP stack?

Here it is giving priority over local lan over wireless and the problem is arised.

Thanks,

I'm still trying to get a clear picture of the layout in my mind. Attached, I've modified your map as much as I could to match what you've told us so far. Could you modify it further to show us what you have, please?
network2.png

Only one more comment.
Why do you want to have a dual connectivity that interfere one with the other ?
Microsoft networking takes some decision based on connection speed and reliability of link.

It normally defaults to wired connectivity so you always have troubles tryng to use two links togheter.

Leave only one link enabled, wired or wireless, not important, and troubles goes away.

Darr247, Thanks for your efforts.

I think now there is no question about that diagram at all. I got the information that the "decision" for forwarding the packate is not based on "the nic it arrived on".  The decision is based on the Destination as it applies to the OS's Routing Table. If the we change something so that decision *could* be based on "the nic it arrived on" then everything will be fine here. but i think Microsoft will not have any API or commands to allow this.

The incomming packets and the outgoing packets are two entirely separate communication streams. They have no relation or effect on each other. So I think the things i am looking for is not possible. I will let you know further details if in some case both the interfaces are mandatory to use.

Thanks

You can try to enable iprouting in the registry. The key is found here
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
\Parameters

IPEnableRouter change the value from 0-1

That will enable the OS to route the packets based on IP that should fix your issue.

Thanks for reply. OS already makes the decision based on the destnation IP. I want the decision should be made based on NIC where packates have been received. If you follow complete thread then you will know that my destination machine is replying to source machine via wired connection(though request arrived at wireless interface) because it will assume that the source machine is in my network. If machine sent the reply on wireless interface then my problem can be solved.

Thanks,
Paresh

Yes I understand what you want just thought maybe enabling the ip routing could solve the problem but as I said in my initial post MS OS decides based on priority. That cannot be changed you could move the wireless up in priority but then the wired will just get the same issues you are having now.

all have helped here a lot but at the end we have to live with our existence problem. Though it is not a bigger issue at the moment I am closing this thread.
Thanks.