switching to direct LAN instead of using WLAN?
Moderators: Hacker, petermad, Stefan2, white
switching to direct LAN instead of using WLAN?
hi,
i frequently synchronize my laptop with my desktop using total commander. all of my machines are set up in a local WLAN, but since i sync moderate amounts of data i tend to tie those two PCs together with a LAN cable.
the problem i'm having is that even after connecting the LAN cable TC still uses the slower WLAN connection; when i want to use the LAN i have to turn off the wifi at least on one of the machines.
is there a way of resolving this isssue? windows' ping naturally switches to LAN when trying to ping.
thanks for any info.
i'm using Win7 64bit & TC7.50a.
i frequently synchronize my laptop with my desktop using total commander. all of my machines are set up in a local WLAN, but since i sync moderate amounts of data i tend to tie those two PCs together with a LAN cable.
the problem i'm having is that even after connecting the LAN cable TC still uses the slower WLAN connection; when i want to use the LAN i have to turn off the wifi at least on one of the machines.
is there a way of resolving this isssue? windows' ping naturally switches to LAN when trying to ping.
thanks for any info.
i'm using Win7 64bit & TC7.50a.
- ghisler(Author)
- Site Admin
- Posts: 50923
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
There has been a discussion about this before - the LAN interface must somehow be given higher priority than the WiFi interface.
Unfortunately I never got this to work, so I have added two buttons to Total Commander to turn WiFi on and off. The buttons call two cmd files containing:
wifienable.cmd:
netsh interface set interface name="WiFi" admin=ENABLED
wifidisable.cmd:
netsh interface set interface name="WiFi" admin=DISABLED
On the buttons, put a "*" in front of the command to ensure that it is run with elevated administrative rights, e.g.:
Command: *wifienable.cmd
Unfortunately I never got this to work, so I have added two buttons to Total Commander to turn WiFi on and off. The buttons call two cmd files containing:
wifienable.cmd:
netsh interface set interface name="WiFi" admin=ENABLED
wifidisable.cmd:
netsh interface set interface name="WiFi" admin=DISABLED
On the buttons, put a "*" in front of the command to ensure that it is run with elevated administrative rights, e.g.:
Command: *wifienable.cmd
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
thanks for the quick answers.
MVV: the LAN cable doesn't connect the PCs to another network, it's a direct connection.
seb-: windows does seem to perform some kind of choosing. for example, when i try 'ping theothermachine' in the command line, while both connections are active, i'm getting <1ms pings (which means it uses the cable connection, otherwise i would be getting pings around 30ms). that's why i was curious how TC handles this and whether it's a windows issue or not.
ghisler & ZoSTeR: thanks for the tips. so it looks like i'll have to decide whether there is any case of WLAN being faster than LAN, and if not, set the network priorities. turning off the wifi by TC buttons seems not to solve the problem, as i can do the same just with the hardware switch.
or do the buttons disable the wifi for TC only? so the network doesn't drop?
MVV: the LAN cable doesn't connect the PCs to another network, it's a direct connection.
seb-: windows does seem to perform some kind of choosing. for example, when i try 'ping theothermachine' in the command line, while both connections are active, i'm getting <1ms pings (which means it uses the cable connection, otherwise i would be getting pings around 30ms). that's why i was curious how TC handles this and whether it's a windows issue or not.
ghisler & ZoSTeR: thanks for the tips. so it looks like i'll have to decide whether there is any case of WLAN being faster than LAN, and if not, set the network priorities. turning off the wifi by TC buttons seems not to solve the problem, as i can do the same just with the hardware switch.
or do the buttons disable the wifi for TC only? so the network doesn't drop?
eidam655,
Even in case of direct Ethernet connection there is a LAN between computers, and both of them must have addresses in it in order to communicate (in such case you have to assign such addresses manually because there is no DHCP server). And if you access laptop via such network-specific IP-address, OS shouldn't be able to find another way via another network interface.
Even in case of direct Ethernet connection there is a LAN between computers, and both of them must have addresses in it in order to communicate (in such case you have to assign such addresses manually because there is no DHCP server). And if you access laptop via such network-specific IP-address, OS shouldn't be able to find another way via another network interface.
You could put the LAN connection in a different subnet.
Let's say your standard WLAN has the subnet 192.168.10.0 / 255.255.255.0.
Computer A has 192.168.10.1
Computer B has 192.168.10.2
Now you have to define a different subnet for the LAN connection
e.g. 192.168.50.0 / 255.255.255.0
Computer A has 192.168.50.1
Computer B has 192.168.50.2
Now you can enter "cd \\192.168.50.1" in the TC command line or Explorer to connect.
Let's say your standard WLAN has the subnet 192.168.10.0 / 255.255.255.0.
Computer A has 192.168.10.1
Computer B has 192.168.10.2
Now you have to define a different subnet for the LAN connection
e.g. 192.168.50.0 / 255.255.255.0
Computer A has 192.168.50.1
Computer B has 192.168.50.2
Now you can enter "cd \\192.168.50.1" in the TC command line or Explorer to connect.