OrganLeroy
Registered
Our home network is a mix of a PC and several Macs. The recent iTunes 10 update (all the machines are now running it) has caused a strange problem with accessing the PC's shared music library from any of the Macs.
When iTunes is first started on the PC, its shared library appears on the Macs' "shared" iTunes column, loads and plays normally for as long as desired.
If the PC sits idle for even 30 minutes or so with none of the Macs playing music from its library, however, that library becomes unavailable. The Macs can see the library in the "shared" iTunes column, but cannot load or play the library.
Quitting and re-starting iTunes on the PC solves the problem, but only temporarily. After another 30 minutes or so of idle time, the shared music library can't be loaded by the Macs.
The problem is asymmetrical in that the PC has no problem loading or playing shared music libraries on any of the Macs. Also, file sharing and printer sharing between the PC and the Macs is unaffected.
The PC is running Windows 7. The Macs are running OS X 10.6.4. The PC has a fixed address on the home network, so DHCP timeout doesn't seem like it can be the culprit here. Any help much appreciated.
When iTunes is first started on the PC, its shared library appears on the Macs' "shared" iTunes column, loads and plays normally for as long as desired.
If the PC sits idle for even 30 minutes or so with none of the Macs playing music from its library, however, that library becomes unavailable. The Macs can see the library in the "shared" iTunes column, but cannot load or play the library.
Quitting and re-starting iTunes on the PC solves the problem, but only temporarily. After another 30 minutes or so of idle time, the shared music library can't be loaded by the Macs.
The problem is asymmetrical in that the PC has no problem loading or playing shared music libraries on any of the Macs. Also, file sharing and printer sharing between the PC and the Macs is unaffected.
The PC is running Windows 7. The Macs are running OS X 10.6.4. The PC has a fixed address on the home network, so DHCP timeout doesn't seem like it can be the culprit here. Any help much appreciated.