[Shakes]

My 12" Powerbook currently uses it's airport extreme card to connect to my current network for internet. The powerbook is currently next to my windows desktp that contains all my MP3's. I want to use the Powerbooks built in ethernet to connect to the PC via a crossover cable while using the Airport card for the shared DSL access. I want to do this because the connection would be much faster than using the 10mbs wireless network

I have it setup and I can ping the internet through the airport card and I can ping the windows box via the ethernet crossover cable. However I can not connect to any of the shares on the Windows box. When I click on "Go -> Connect to Computer" I see the windows box twice. One for the wireless lan and one for the crossover cable. However when I click on it and try to connect it just times out. If I remove the crossover cable I can connect to the shares fine over the wireless lan. Any ideas?

I am using DHCP on the Powerbook for the wireless lan with an IP address of 192.168.0.100 and I am specifiying the ethernet address of 192.168.100.2. The windows box has an IP address of 192.168.0.2 for the wireless lan and an IP address of 192.168.100.1.

Thanks

[ghporter]

You do have the folder full of MP3s shared on the Windows box, don't you? No password or anything, full access rights and so on? You don't mention which Windows version it uses, so I can't give you any direct help there, but if it ain't shared, it won't be available.

Now, how are you trying to access the Windows volume? Are you using Samba or something else? Samba should be the first choice; it's very powerful, and (really the best part!) it comes with OS X. Unfortunately, it's not trivial to just say "open the Samba control panel and do..." Mainly 'cause there's no such animal-most of Samba is configured through the Terminal. There is, however, plenty of help, primarily online, for configuring Samba. Browse through this forum for a while and you'll find dozens of entries for how to share a Windows volume with Samba.

[Camelot]

The problem isn't with samba setup on the Mac - he's trying to connect the Mac to the Windows shares, so samba doesn't even need to be running to make this happen.

The problem is that there are dual paths between the Mac and the PC - one via wireless and one via wired, and they're all in the same subnet. The systems are getting confused about which NIC the traffic should pass on.

You should configure the ethernet ports (connected via crossover cable) so they use a completely different range of IP addresses (such as 10.1.1.1 and 10.1.1.2). Then when you connect to the Windows machine, specify the 10.1.1.2 address, and there won't be any confusion for the system as to which NIC to use.

[ghporter]

Originally posted by Camelot:
The problem isn't with samba setup on the Mac - he's trying to connect the Mac to the Windows shares, so samba doesn't even need to be running to make this happen.

The problem is that there are dual paths between the Mac and the PC - one via wireless and one via wired, and they're all in the same subnet. The systems are getting confused about which NIC the traffic should pass on.

Can't you tell Samba to use a particular NIC for a particular connection or protocol?