Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
This forum is in permanent archive mode. Our new active community can be found here.
Network connection priority troubles
Here's an odd pickle...
My 'home' (as in dorm room) network is an interesting concoction of salvaged networking gear. I have an old Deskpro running DHCP and Samba servers under Debian, a Digital DecHUB One that's probably about as old as I am, and a La Fonera I nabbed for free that I've loaded with DD-WRT.
The exact flow from component to component in my room is as follows:
WAN <---> Fonera (Serving 192.168.0.x) <--(wireless)--> Laptop <---> DecHUB <---> Deskpro (Serving 10.0.0.x)
Yes, it's roundabout, but it keeps my server off the WAN. I've considered every possible arrangement of equipment, and this is the best setup I've found (Deskpro is too slow to route traffic, Fonera doesn't have a LAN Ethernet jack to serve DHCP addresses, etc). Now, the trouble I'm having isn't related to the equipment itself, but how my laptop is deciding which connection to use.
I'm currently dual-booting Gutsy and Windows XP Pro. Under Gutsy, everything is fine and dandy, I can get at my files and the Internet. When I boot into XP, if I try to use both connections simultaneously, things fall to pieces. I've tried renaming the connections, adjusting their priorities under Network Connections > Advanced > Advanced Settings, readjusting the Fonera to serve 1.0.0.x addresses (I thought it might be alphabetizing the IP addresses), and rebooting a bajillion times. Since I use Gutsy more than XP, it's not a huge problem, except that DC++ adaptations for Linux are... not that great. Without proper access to both networks under XP, I can't connect to the school's internal hub and share my files simultaneously.
It almost seems like XP internally gives priority to physical connections. Any ideas on how to force Windows to get it right?
My 'home' (as in dorm room) network is an interesting concoction of salvaged networking gear. I have an old Deskpro running DHCP and Samba servers under Debian, a Digital DecHUB One that's probably about as old as I am, and a La Fonera I nabbed for free that I've loaded with DD-WRT.
The exact flow from component to component in my room is as follows:
WAN <---> Fonera (Serving 192.168.0.x) <--(wireless)--> Laptop <---> DecHUB <---> Deskpro (Serving 10.0.0.x)
Yes, it's roundabout, but it keeps my server off the WAN. I've considered every possible arrangement of equipment, and this is the best setup I've found (Deskpro is too slow to route traffic, Fonera doesn't have a LAN Ethernet jack to serve DHCP addresses, etc). Now, the trouble I'm having isn't related to the equipment itself, but how my laptop is deciding which connection to use.
I'm currently dual-booting Gutsy and Windows XP Pro. Under Gutsy, everything is fine and dandy, I can get at my files and the Internet. When I boot into XP, if I try to use both connections simultaneously, things fall to pieces. I've tried renaming the connections, adjusting their priorities under Network Connections > Advanced > Advanced Settings, readjusting the Fonera to serve 1.0.0.x addresses (I thought it might be alphabetizing the IP addresses), and rebooting a bajillion times. Since I use Gutsy more than XP, it's not a huge problem, except that DC++ adaptations for Linux are... not that great. Without proper access to both networks under XP, I can't connect to the school's internal hub and share my files simultaneously.
It almost seems like XP internally gives priority to physical connections. Any ideas on how to force Windows to get it right?
Comments
Thanks again guys!
Ohh that is actually very smart. How did you do that in XP?