New
#11
How to set up ethernet connection preference over WiFi network?
-
-
New #12
Temporarily enable the wireless network adapter on the XP box.
See if pings to the XP box work. If they fail, get that fixed first.
Temporarily disable the wireless network adapter on the XP box and the W7 box.
See if pings to the XP box work.
After the test, you can enable the wireless network adapter on the W7 box again.
-
New #13
Yes, I'll be able to ping the XP machine if I enable WiFi back. (One caveat in this case is that I need to remove static IP from the ethernet connection, as otherwise XP shows "Limited connectivity" warning for the WiFi. It might be an XP bug though.)
You see, my initial idea was to have both WiFi and ethernet connections -- WiFi for the Internet and ethernet for fast connection between computers. But evidently there's some internal conflict in this configuration that Windows doesn't like that I don't really understand...
-
New #14
I knew what you hoped to do. I was just testing one part at a time.
The OS normally only uses one network adapter* at a time, but some people have managed to do what you want. Maybe other forum members know how to do that... I don't.
*the fastest adapter - hence, XP picking the wired one and not seeing an Internet connection via wired - so, limited connectivity warning. On your W7 box, the wireless adapter might claim to be the fastest.Last edited by UsernameIssues; 03 Oct 2015 at 14:15.
-
New #15
So... you want each PC to access the internet through wifi, but network to each other through a wired connection? Do you have anything else connecting through the wifi to the PCs, like a printer or NAS? if not, then you can try this setup:
1. Use a different subnet (e.g. 192.168.2.0) for the wired NIC like this:
1.a. On PC1's wired NIC, set a static IP address of 192.168.2.1, mask 255.255.255.0. NO default route or DNS entres; leave them blank.
1.b. On PC2's wired NIC, do the same as above but IP address 192.168.2.2.
2. Your wifi settings should have the default route and DNS entries already, if you've changed anything there, put it back how it was.
Now, anything going off either of your subnets (192.168.1.0 and 192.168.2.0) to somewhere else will use the default route to the wifi router.
3. On both PC's WiFi settings (LAN properties), untick "Client for Microsoft Networks" and "File and Printer Sharing for Microsoft Networks".
Now, the PCs should be forced to use the wired NIC for file sharing. Removing the above prevents Windows from using its file sharing protocols on those interfaces.
After changing the above, it takes a good few seconds for things to stabilise. I tried it out and verified it worked between two XP virtual machines, but the principle is the same for Windows 7.
An alternative to removing the file sharing services on the NICs might be to enable some sort of Private/Isolated setting on your WiFi router. Check your manual. What you are looking for is a setting that prevents WiFi-connected PCs from communicating with each other through the router. Many WiFi routers have this facility for security. That will probably have the same effect as my instructions. You should still use a different subnet for the wired LAN though.Last edited by foxyrick; 03 Oct 2015 at 13:08. Reason: speeling
-
New #16
Thank you for trying to help, guys!
Yes, I do have other things on this WiFi network. I thought it wouldn't matter in my original post, but now I see that it may. So let me give you the full configuration:
1) Windows 7 desktop:
- I have VMWare Workstation 10 set up on it that comes with two of its own (virtual) networks/adapters used for its guest OS'es.
- The WiFi network provides Internet connection to a Comcast broadband modem.
- The Wifi network is connecting this computer to another Windows 7 desktop (in my office) that has its laser printer sharing enabled.
- The WiFi network also connects this computer to an all-in-one fax machine/scanner/color/photo printer.
2) Windows XP desktop:
- The WiFi network provides Internet connection to a Comcast broadband modem.
- (I do not print nor scan from this PC.)
The reason I'm trying to set up this ethernet connection between XP and Win7 machines, is that the XP machine has some proprietary software installed on it (needing special hardware) that generates bulky data files that I need to send to the Win7 machine. My original approach was to use an external/portable hdd for that, but it seemed like a slow and tedious process of plugging it in and out, (unfortunately XP machine doesn't have front-facing USB ports) then transferring those large files to and from hdd, etc. So I thought that setting up a shared folder via ethernet cable was a simpler/faster solution. But now as I look at how complicated it is to set it up, maybe using an external hdd wasn't that complicated after all :)
So @foxyrick, shall I still try your suggestions?
-
New #17
That changes things. Don't disable the file sharing services, because then you'll lose printing etc.
Whether my final paragraph will still work depends entirely on the capabilities of your wifi router and braodband modem. I'm not familiar with your hardware so can't say, but that is the way to go (investigate) if you still want to do this. I know I could do it on my network (and it's a *lot* more complicated that yours) but it does depend on your kit's capabilities.
There's even the possibility to have a second wifi SSID and subnet/VLAN for the XP PC, so that it isn't even on the same wifi network and has to use the wire to talk to the other PC. Again, it depends on your kit.
Edit to add: It might be as simple as ticking a 'privicy' box on your wifi router's settings, if it does that. Or not...
Quote
Related Discussions