Dual LAN connection problem

[Holger Winnemoeller]

I am using a setup where I have two computers running XP that connect
to the internet via wireless. Sometimes I want to connect these two
computers directly for fast transfer of large files (wireless would be
too slow), but when I connect the wired connection (which works) the
wireless stops functioning properly (it is still connected, but cannot
resolve IP addresses etc., although the DNS server didn't change).

What I imagine is that windows thinks: hey there is now a wired
connection, let's use that for everything instead, but of course, there
is no internet connection on the wired LAN.

Anyone know how to fix this problem, i.e. get both Wireless to continue
serving internet connections and wired LAN for intranet connections.

Any help is appreciated.

 

[Steve Winograd [MVP]]

I am using a setup where I have two computers running XP that connect
to the internet via wireless. Sometimes I want to connect these two
computers directly for fast transfer of large files (wireless would be
too slow), but when I connect the wired connection (which works) the
wireless stops functioning properly (it is still connected, but cannot
resolve IP addresses etc., although the DNS server didn't change).

What I imagine is that windows thinks: hey there is now a wired
connection, let's use that for everything instead, but of course, there
is no internet connection on the wired LAN.

Anyone know how to fix this problem, i.e. get both Wireless to continue
serving internet connections and wired LAN for intranet connections.

Any help is appreciated.

These steps should do what you want:

1. Assign static IP addresses to the wired network connections, using
a different subnet than the wireless connections. For example, if the
wireless connections use 192.168.1.x, assign 192.168.2.1 and
192.168.2.2 to the wired connections.

2. Don't assign a Default Gateway address to the wired connections.

3. When you want to use the wired connection, refer to the other
computer using its IP address, not its computer name. An easy way to
do that is to type the address in the Start | Run box, preceded by two
backslahes. For example:

\\192.168.2.1
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Holger Winnemoeller]

Thanks Steve,

I can confirm that these steps do work: I can see each of the computers
now and the wireless still works. Well done and thanks for the great
info. Now, being in IT myself, but not a networking specialist I am
still interested as to what the problem is that your instructions
fixed. Also: using a wired IEEE1934 connection I don't have any hassles
(of course it's not that easy to find a 60 foot firewire cable , so
what does windows think is the difference is here to an Ethernet
connection?

Holger.

 

[Holger]

3. When you want to use the wired connection, refer to the other

computer using its IP address, not its computer name. An easy way to
do that is to type the address in the Start | Run box, preceded by two
backslahes. For example:

\\192.168.2.1

Just as a quick addendum:
Following the above steps I could simply use my original Hostname
instead of having to resort to the IP address. I.e. step 3 wasn't
necessary. Even better!

 

[Steve Winograd [MVP]]

Just as a quick addendum:
Following the above steps I could simply use my original Hostname
instead of having to resort to the IP address. I.e. step 3 wasn't
necessary. Even better!

Good -- your computers are resolving the host names to the wired
connection IP addresses, not to the wireless connection IP addresses.
That's not always the case, and using IP addresses instead of names is
a sure way to get the right connection.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Steve Winograd [MVP]]

Thanks Steve,

I can confirm that these steps do work: I can see each of the computers
now and the wireless still works. Well done and thanks for the great
info. Now, being in IT myself, but not a networking specialist I am
still interested as to what the problem is that your instructions
fixed. Also: using a wired IEEE1934 connection I don't have any hassles
(of course it's not that easy to find a 60 foot firewire cable , so
what does windows think is the difference is here to an Ethernet
connection?

Holger.

You're welcome, Holger.

For LAN use, my instructions access the other computer using its wired
IP address to ensure that the wired connection is used. If you access
the other computer using its computer name, either of the connections
could be used, depending on which IP address the computer name is
resolved to. That's the same whether there are two Ethernet
connections or one Ethernet and one IEEE1394.

Internet access uses the Default Gateway address. Not assigning one
to the wired connection ensures that Internet access will use the
wireless connection.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com