Re: How to isolate issue with app that works on Lion but not on Mountain Lion
Re: How to isolate issue with app that works on Lion but not on Mountain Lion
- Subject: Re: How to isolate issue with app that works on Lion but not on Mountain Lion
- From: Peter Teeson <email@hidden>
- Date: Sun, 29 Dec 2013 15:54:47 -0500
On 2013-12-28, at 8:36 PM, Peter Teeson <email@hidden> wrote:
> As a P.S. to the above both the server and the console app debug logs indicate it's not a Java issue since they are both functioning normally except for (maybe UPNP).
> It seems somewhat likely that it might be something to do with setting up a UPNP task and communicating through the en0 port.
>
> This is Mountain Lion 10.8.5 we're talking about. Were there any changes wrt using ethernet? Different timeouts for ports or anything like that?
> I didn't see anything mentioned in the What's New notes.
Further info I have gleaned from the logs.
Apparently there is a multicast search message broadcast from eno at 192.168.2.10
On Lion it gets a response from the Renderer a.k.a. TV with DLNA at 192.158.2.15
But on Mountain Lion no response within the timeout which is = 0.
So how is it that the identical code works on Lion but not on ML?
It's years since I did any networking stuff and that was on IBM mainframes so my knowledge for this environment is nil.
Suggestions? So far the authors have not replied to my postings in their forum.
respect….
Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden