UNSOLVED
SS
SMM Sweden AB
5 Posts
0
14978
October 19th, 2005 07:00
Problem: Wireless connection lost when plugging in wired network
Hi
We have a couple of X200;s running Win XP SP2 and they are always docked. We need to connect a few ADAM modules by wired network while at the same time stay connected to the server over wireless network.
I have done this exact operation on a few different stationary PC;s (non-branded, OptiPlex GX150, OptiPlex GX170L) without any problems, sometimes using Win XP bridging (to allow the server to see the ADAM modules) and sometimes not. No problems.
With nothing connected to the wired network port I can fully access the server (over wireless). Pinging the server works ok.
The second I connect something to the wired network port I lose contact with the wireless network and have full contact on the wired network. Network connection status claims both networks are connected. IPCONFIG reports 2 different IP adresses for the cards, both in the same subnet (ie 192.168.123.211 and 192.168.123.222 in subnet 255.255.255.0). Ping makes contact with machines on the wired network but not with server on wireless.
A few seconds after unplugging the wired network I gain access to the wireless network again and pinging the server is ok.
All hardware shows ok in the hardware list on all computers involved. Drivers, BIOS and Win XP all fully updated. All energy saving turned off. Have tried using different subnets for wired and wireless (ie 192.168.123 for one and 192.168.0 for the other). Have tried both fixed and automatic IP adresses. All combinations give the same result.
HELP!!!!!
We have a couple of X200;s running Win XP SP2 and they are always docked. We need to connect a few ADAM modules by wired network while at the same time stay connected to the server over wireless network.
I have done this exact operation on a few different stationary PC;s (non-branded, OptiPlex GX150, OptiPlex GX170L) without any problems, sometimes using Win XP bridging (to allow the server to see the ADAM modules) and sometimes not. No problems.
With nothing connected to the wired network port I can fully access the server (over wireless). Pinging the server works ok.
The second I connect something to the wired network port I lose contact with the wireless network and have full contact on the wired network. Network connection status claims both networks are connected. IPCONFIG reports 2 different IP adresses for the cards, both in the same subnet (ie 192.168.123.211 and 192.168.123.222 in subnet 255.255.255.0). Ping makes contact with machines on the wired network but not with server on wireless.
A few seconds after unplugging the wired network I gain access to the wireless network again and pinging the server is ok.
All hardware shows ok in the hardware list on all computers involved. Drivers, BIOS and Win XP all fully updated. All energy saving turned off. Have tried using different subnets for wired and wireless (ie 192.168.123 for one and 192.168.0 for the other). Have tried both fixed and automatic IP adresses. All combinations give the same result.
HELP!!!!!
SMM Sweden AB
5 Posts
445
0
Posted October 20th, 2005 04:00
There must be a way. It works on all other systems I have tried it on. I've even done it with two 10/100 NICs plus a wireless card. They were all desktop systems, but I do not believe they change the wiring on notebooks. I do not think it is an OS problem either since all our machines run Win XP Pro fully updated.SMM Sweden AB
5 Posts
445
0
Posted October 20th, 2005 05:00
Of course you can. This has been the prefered and recommended way to achieve routing and bridging (ie internet sharing) since Win98 or earlier... One NIC to the DSL/internet/external network, and one to your home/office network. And, as I have stated before, I have it running on several machines already - both wired/wired, wired/wireless and wired/wired/wireless combos. The only problem is that these notebooks behave differently. I think it must be a driver or setting issue.SMM Sweden AB
5 Posts
445
0
Posted October 20th, 2005 06:00
Well, actually that was an oversimplification to visualize the type of problem...
Actually we have the following scenario:
We are putting together a measuring system which must be light weight (air transport as carry-on luggage, hence the notebooks), easy and quick to install at various factories (hence wireless between server and clients) and connect as securely as possible (timeouts/dropped communication unacceptable) to the ADAM measuring devices (hence wired from client to ADAM). We also do not know in advance the distances, so the kit will include one AP and one repeater per client. We should be able to drop the AP and run in ad-hoc, but keeping an AP makes it simpler to connect to our network back at the office.
I have a new lead which might actually solve the problem. Will test it and post my results here...SMM Sweden AB
5 Posts
445
0
Posted October 20th, 2005 08:00
It seems like you need to force specific (unique) IP addresses on all network cards (wired and wireless) to make it work in the notebooks. After creating the network bridge you also need to force a unique IP address for the bridge (ie setting wired NIC to 192.168.123.2, wireless to 192.168.123.3, make the bridge, set bridge to 192.168.123.4). On all other systems I have installed this everyting worked using automatic settings...
jmwills
2 Intern
•
11984 Posts
445
0
Posted October 19th, 2005 13:00