svn-1571 not working after upgrading to iTunes 7.3.1.3

[gerhardParticipant]

Never touch a running system, a wise man once said.
Just upgraded to the latest Itunes version (W2K) and cannot play my music any more. The share is show, and as everything worked with iTunes 7.1.something, i guest apple changed something to make people angry 😉

Should I upgrade to the latest svn ? or provide more details.
iTunes shows an error -3259 (Cannot access shared library (translated from german version)) and says that I should open firewall port 3689. But since previous versions of iTunes worked flawless, this error message must be wrong.

The log file says nothing 🙁

Gerhard

[rpeddeParticipant]

@gerhard wrote:

Never touch a running system, a wise man once said.
Just upgraded to the latest Itunes version (W2K) and cannot play my music any more. The share is show, and as everything worked with iTunes 7.1.something, i guest apple changed something to make people angry 😉

Should I upgrade to the latest svn ? or provide more details.
iTunes shows an error -3259 (Cannot access shared library (translated from german version)) and says that I should open firewall port 3689. But since previous versions of iTunes worked flawless, this error message must be wrong.

The log file says nothing 🙁

Gerhard

Can you http to port 3689 on the server? Something like http://server.ip.addr:3689?

Usually that means that the server isn’t running, since iTunes can’t make a connection.

[gerhardParticipant]

@rpedde wrote:

Can you http to port 3689 on the server? Something like http://server.ip.addr:3689?

Usually that means that the server isn’t running, since iTunes can’t make a connection.

Yes. And I can connect and play via other clients (Roku, rhythmbox). Strange.

[gerhardParticipant]

running mt-daapd with -d 9 just gives me a few select … lines, nothing more. I also deleted the iTunes forder in the MyMusic folder without success. iTunes says it is loading data from the selected share, but stops with the posted error message after ~ 15 secs. Looks like it doesn’t even try to connect to the share (since there’s no log entry and I’m sure there would be one when a client connects to the server)

Gerhard

[rpeddeParticipant]

@gerhard wrote:

running mt-daapd with -d 9 just gives me a few select … lines, nothing more. I also deleted the iTunes forder in the MyMusic folder without success. iTunes says it is loading data from the selected share, but stops with the posted error message after ~ 15 secs. Looks like it doesn’t even try to connect to the share (since there’s no log entry and I’m sure there would be one when a client connects to the server)

Gerhard

Any kind of third party firewall? VPN software? Anything crazy like that? My cisco vpn software sometimes flakes out my routing tables on my mac. 🙁

[gerhardParticipant]

@rpedde wrote:

Any kind of third party firewall? VPN software? Anything crazy like that? My cisco vpn software sometimes flakes out my routing tables on my mac. 🙁

No.No. No. Did the update from 7.0.2.16 to 7.3.1.3 yesterday also on my laptop (also W2K). Before the upgrade iTunes could play, afterwords no even connect the share. That’s really weird.

Btw, is there any standard for characters in the sharename, since I use “mt-daapd” as share name, but as iTunes can see it (and could play it in previous versions) that should be OK.

Gerhard

[rpeddeParticipant]

@gerhard wrote:

@rpedde wrote:

Any kind of third party firewall? VPN software? Anything crazy like that? My cisco vpn software sometimes flakes out my routing tables on my mac. 🙁

No.No. No. Did the update from 7.0.2.16 to 7.3.1.3 yesterday also on my laptop (also W2K). Before the upgrade iTunes could play, afterwords no even connect the share. That’s really weird.

Btw, is there any standard for characters in the sharename, since I use “mt-daapd” as share name, but as iTunes can see it (and could play it in previous versions) that should be OK.

Gerhard

Maybe it’s a windows thing. My macs seem okay. I’ll try a windows machine at work tomorrow.

— Ron

[gerhardParticipant]

@rpedde wrote:

Maybe it’s a windows thing. My macs seem okay. I’ll try a windows machine at work tomorrow.

— Ron

Does anyone else have this problem with the latest iTunes under W2K, or do my problems discourage anyone from upgrading ? As there’s nothing in the log, it seems iTunes does’nt even try to connect.
I thought, that maybe proxy settings are taken from the web browser, but the web proxy logs don’t show any connections either.

And the subject should of course be ” iTunes in the latest version not working with mt-daapd” 😉 I can (still) connect via Soundbridge and rhythmbox without any problems.
Will try to downgrade iTunes this evening, that shold do it.

Gerhard

[Bramfm]

@gerhard wrote:

Does anyone else have this problem with the latest iTunes under W2K, or do my problems discourage anyone from upgrading ? As there’s nothing in the log, it seems iTunes does’nt even try to connect.
I thought, that maybe proxy settings are taken from the web browser, but the web proxy logs don’t show any connections either.

And the subject should of course be ” iTunes in the latest version not working with mt-daapd” 😉 I can (still) connect via Soundbridge and rhythmbox without any problems.
Will try to downgrade iTunes this evening, that shold do it.

Gerhard

I have exactly the same problem with the latest version of iTunes and XP.

[rpeddeParticipant]

@Bramfm wrote:

@gerhard wrote:

Does anyone else have this problem with the latest iTunes under W2K, or do my problems discourage anyone from upgrading ? As there’s nothing in the log, it seems iTunes does’nt even try to connect.
I thought, that maybe proxy settings are taken from the web browser, but the web proxy logs don’t show any connections either.

And the subject should of course be ” iTunes in the latest version not working with mt-daapd” 😉 I can (still) connect via Soundbridge and rhythmbox without any problems.
Will try to downgrade iTunes this evening, that shold do it.

Gerhard

I have exactly the same problem with the latest version of iTunes and XP.

I noticed that on mac, with latest bonjour it’s trying to connect to the IPv6 address, not the IPv4 one. Wonder if that’s it?

I’ll try and add IPv6 to the next build. I’ve merged up the test branch into the mainline branch, and hope to have it cleaned up and compilable again on windows in a day or two.

— Ron

[gerhardParticipant]

@rpedde wrote:

I noticed that on mac, with latest bonjour it’s trying to connect to the IPv6 address, not the IPv4 one. Wonder if that’s it?

I’ll try and add IPv6 to the next build. I’ve merged up the test branch into the mainline branch, and hope to have it cleaned up and compilable again on windows in a day or two.

— Ron

You’re right, a look at the firewall logs shows an IPv6 entry:
Aug 1 18:29:53 router2 Unknown InputIN=eth0 OUT= MAC=00:01:80:5c:08:91:00:0c:6e:e5:e2:31:08:00 SRC=10.0.0.3 DST=10.81.8.6 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=59320 DF PROTO=TCP SPT=4539 DPT=3689 WINDOW=65535 RES=0x00 SYN URGP=0

the source is from my internal network, that’s ok, but the destination is the address of the external NIC (the one connected to the DSL router) of the mt-daapd server.
I changed mDNSResponder to listen only on the internal NIC (parameter -i interface) and – voila – everything works as before.

Gerhard

[rpeddeParticipant]

@gerhard wrote:

@rpedde wrote:

I noticed that on mac, with latest bonjour it’s trying to connect to the IPv6 address, not the IPv4 one. Wonder if that’s it?

I’ll try and add IPv6 to the next build. I’ve merged up the test branch into the mainline branch, and hope to have it cleaned up and compilable again on windows in a day or two.

— Ron

You’re right, a look at the firewall logs shows an IPv6 entry:
Aug 1 18:29:53 router2 Unknown InputIN=eth0 OUT= MAC=00:01:80:5c:08:91:00:0c:6e:e5:e2:31:08:00 SRC=10.0.0.3 DST=10.81.8.6 LEN=48 TOS=0x00 PREC=0x00 TTL=128 ID=59320 DF PROTO=TCP SPT=4539 DPT=3689 WINDOW=65535 RES=0x00 SYN URGP=0

the source is from my internal network, that’s ok, but the destination is the address of the external NIC (the one connected to the DSL router) of the mt-daapd server.
I changed mDNSResponder to listen only on the internal NIC (parameter -i interface) and – voila – everything works as before.

Gerhard

aha. looks like the new itunes tries ipv6 before ipv4 now.

[dscyclerParticipant]

But if you ARE running ipv6 as well as ipv4 things seem OK both with Vista and XP with iTunes 7.3.1.3 and svn-1586 (running on Vista). Firefly Server shows up in iTunes just fine.

[gerhardParticipant]

@dscycler wrote:

But if you ARE running ipv6 as well as ipv4 things seem OK both with Vista and XP with iTunes 7.3.1.3 and svn-1586 (running on Vista). Firefly Server shows up in iTunes just fine.

99 % of all users probbably don’t run IPv6, and showing up is not enough. The Firefly Server was shown in iTunes on my machine, but connecting was not possible.
BTW, I think this is either an error in iTunes or mDNSResponder, because why the hell iTunes thinks it should connect to a wrong IP (in case the Server has 2 NIC’s).

Gerhard

[rpeddeParticipant]

@gerhard wrote:

@dscycler wrote:

But if you ARE running ipv6 as well as ipv4 things seem OK both with Vista and XP with iTunes 7.3.1.3 and svn-1586 (running on Vista). Firefly Server shows up in iTunes just fine.

99 % of all users probbably don’t run IPv6, and showing up is not enough. The Firefly Server was shown in iTunes on my machine, but connecting was not possible.
BTW, I think this is either an error in iTunes or mDNSResponder, because why the hell iTunes thinks it should connect to a wrong IP (in case the Server has 2 NIC’s).

Gerhard

The apple mDNS responder is pretty stupid on non-osx machines. Really, on linux machines avahi is the way to go, now that it’s stabilized.

Seems like thre was an update to iTunes in the last day or two to 7.3.2. I wonder if that fixes that problem. Haven’t gotten to look closely at it yet.

[Author]

Posts