[gomariners]

So here's the problem: many people use a wireless router at my work, some people use the wired. The wireless is plugged into the same network, but people using wireless can only discover each other, not people on wired. Is there a way, especially as we add wireless routers, to allow people to discover libraries under these NAT routers? I've tried various suggestions, but so far, nothing works!

[C.J. Moof]

Interesting. I have a similar problem- my office is covered by 4 original Airport bases, all with the same name, so wireless users seamlessly roam between them. When 2 users are both on airport, they'll see each other in iTunes, but if you try to load their music, it just does nothing, until it finally asks:



Everything is fine if one of the 2 computers is on ethernet. If they're both wireless, they can discover, but not move any data across itunes.

I also can't SSH to the client from either it's .local name, or IP address this way.

I sure wish I knew why mac <-> airport <-> switch <-> airport <-> mac communication can't be done here.

[Millennium]

gomariners: Are the wired and wireless networks on different subnets? If so, then I'm afraid you're out of luck; iTunes sharing only works between machines on the same subnet. This is not a bug; Apple did it on purpose.

C. J. Moof: It's strange that you would be able to discover each other's stuff but not be able to transfer data. Is it possible that your system administrators are deliberately blocking these ports, and have overlooked the iTunes discovery port?

[gomariners]

Originally posted by Millennium:
gomariners: Are the wired and wireless networks on different subnets? If so, then I'm afraid you're out of luck; iTunes sharing only works between machines on the same subnet. This is not a bug; Apple did it on purpose.

C. J. Moof: It's strange that you would be able to discover each other's stuff but not be able to transfer data. Is it possible that your system administrators are deliberately blocking these ports, and have overlooked the iTunes discovery port?

Yeah, I know about that Apple purposefully stopping me thing. It's like this, the wireless router is on the same subnet as I am, and then the people accessing the wireless see themselves on the subnet of the NAT router. But they are under my subnet, if you know what I mean like



Any hope?

[C.J. Moof]

Originally posted by Millennium:

C. J. Moof: It's strange that you would be able to discover each other's stuff but not be able to transfer data. Is it possible that your system administrators are deliberately blocking these ports, and have overlooked the iTunes discovery port?

I am the system admin. I'm not blocking anything within the LAN, at least not by any intentional choice. I want the music to flow- John Kerry has some good stuff! We're all on the same subnet, with addresses served from the same DHCP server.

One of these days I'll sit down and capture packets and try to figure this all out. At this point I can't venture a guess what I'd change to make it work.....

[SSharon]

Its by no means an explanation or real solution but I remember reading something about sharing over 2 subnets on macosxhints.com I don;t remember all the details, so you will have to search for the article but it had something to do with adding another network connection in the pref panes and sort of using both at the same time, the point being that each connection is in the one location you have selected and that they have different subnets so you can see both. If that makes no sense, well a)I'm not surprised and b)search for it or let someone smarter explain it

[C.J. Moof]

Originally posted by C.J. Moof:
I am the system admin. I'm not blocking anything within the LAN, at least not by any intentional choice. I want the music to flow- John Kerry has some good stuff! We're all on the same subnet, with addresses served from the same DHCP server.

One of these days I'll sit down and capture packets and try to figure this all out. At this point I can't venture a guess what I'd change to make it work.....

Just a followup to this topic- after upgrading both computers to iTunes 4.7, this doesn't happen any longer.