|
|
How do I force routing through network port?
|
|
|
|
Fresh-Faced Recruit
Join Date: Mar 2006
Status:
Offline
|
|
I just bought a 17" iMac to go along with my 1.83GHz MacBook. For internet, I have both connecting to my router via wireless, and have run a CAT5 cable directly between the wired network ports, to facilitate Gigabit networking between the two machines without buying a separate Gigabit switch.
Testing indicates that transferring files between the two machines is still going through the wireless router, rather than using the direct physical connection. What's the easiest way to force the two machines to use the Gigabit connection rather than the wireless? They are both self-assigning DHCP addresses that seem to be correct.
Thanks for any pointers.
Rick
|
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2005
Location: Cambridge, UK
Status:
Offline
|
|
Turn off the wireless on one of them temporarily.
|
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Mar 2006
Status:
Offline
|
|
Will that work permanently, or do I need to do it whenever I want to transfer between the two machines? I'm going to try it, of course - just curious about what I'll find in the long run.
I know how to do this between a Windows box and a Mac, and have done it - I set static IPs on both boxes, then set up a UNC share through the IP on the Windows box, rather than through the machine name. Is there a way to do that between two Macs?
|
|
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2001
Location: Utah
Status:
Offline
|
|
You can basically do the same thing with OSX; just setup a static network that is different from the network that your wireless DHCP server assigns. Then, when you want to share folders between them in the Finder, use the IP rather than the name (just to be sure).
|
|
|
|
|
|
|
|
|
Mac Elite
Join Date: May 1999
Location: San Jose, CA
Status:
Offline
|
|
You don't need to use any special routing - the OS will take care of this automatically if you setup your network correctly.
Since it isn't working I'm guessing you set the IP address of the wired link in the same subnet as the wireless network, and that's the mistake.
What you need to do is setup a different subnet on the wired link. For example, if your wireless network is using 192.168.1.x, configure the wired network with 10.1.1.x.
Now, from either machine you can access the 192.168.1.x address of the other machine to use the wireless network, or use the 10.1.1.x address to use the wired network.
|
Gods don't kill people - people with Gods kill people.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|