#29

New

Connection issues

Reported by hyder on TuneConnect for Mac/PC · 04/02/2008 20:15:38

Assigned to:
Matt Patenaude
Priority:
Low
Status:
New
Category:
General Malfunction
Version:
2.0 Beta 1
Platform:
10.4.11, 2G Duo

About half the time, it won't connect to the server. I have to quit and restart each time. I don't see any debug info, so I don't know what else I can give you on this.

Also, as a feature request, you should probably have some way to return to the server list if things go bad...


Attachments Upload

No attachment has been uploaded, yet.


6 comments so far

Matt Patenaude

7 months ago

Sounds like it could be a Tiger issue, but not sure-- post the console.log file so I can see what's going on.

hyder

7 months ago

Oh, duh. Here's one. Looks like it sometimes doesn't get the IP.

Attachments:

Matt Patenaude

7 months ago

Well that's indeed quite interesting. If I had to wager a guess... hm. I wouldn't. :P

I've never experienced that issue, and I can't duplicate it. If I had to guess, for now, I'd say it's a Tiger issue, but that doesn't really make any sense either. Is it the client you have to restart, or the server?

hyder

7 months ago

Restarting the client works (sometimes takes a few tries, however, as you can see from the log). I haven't tried restarting the server.

Matt Patenaude

7 months ago

Well if restarting the client works, then it's 99.99% likely that the error occurs in the interpretation of the Bonjour record, rather than in the publishing of the Bonjour record. C functions are sticky to deal with. It doesn't make sense to me that it'd be a Tiger only bug (then again, sporadic bugs never make sense :P), but I really don't know how to proceed with this. I'll take a look at it, though.

hyder

7 months ago

Hmm. It happens pretty frequently (50% +), but I can't see any common thread as to when it will work. Turns out I was just impatient, as it does return to the server list after several seconds. And, after the return, and can try to connect again and it sometimes works. So, a client restart is NOT required.

Hopefully I'll find something more...

Leave a comment