search

archienz / ps3mediaserver

Automatically exported from code.google.com/p/ps3mediaserver
0 stars 0 forks source link

[Network] PS3 doesn't reply to network announcement on PMS restart #104

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
What is the expected output? What do you see instead?
1. Launch PMS
2. PS3 replies to PMS
3. Close PMS
4. Relaunch PMS
5. PS3 does not reply to PMS

What version of the product are you using? On what operating system?
PMS v1.02.1, although issue has been around since v0.99
Win XP, SP3
PC <-(Wireless G)-> Router <-(Wired Ethernet)-> PS3

Please provide any additional information below...
I'm able to successfully launch PMS and have the PS3 reply if I completely
restart everything (PC, router, PS3) or if I wait some extended length of
time (hours) with PMS not running.

Once I shutdown PMS, netstat shows Port 5001 as correctly closing the
connection (the server correctly goes away from the PS3 XMB), although
sometimes it briefly lingers around.  It doesn't matter when I try to
relaunch PMS (right away with the old connection lingering or once the
connection is closed), the relaunch is still unsuccessful.

After I relaunch PMS, the trace and debug.log show PMS correctly sending
the alive notice to the PS3, but the PS3 doesn't reply.  Netstat shows Port
5001 as Listening at this point.  If I force a different port in the PMS
settings (and setup the proper access in my router port forwarding and
software firewall) and then restart PMS, the PS3 replies the first time but
not on relaunch.

Attached are Wireshark (a network packet sniffer) captures for both cases
(PMS in XMB, PMS not in XMB) filtered for UPnP announcements through
239.255.255.250 and for Port 5001 traffic.  192.168.0.199 is my PC and
192.168.0.198 is my PS3, with both IPs statically assigned by my router.

Original issue reported on code.google.com by meskibob@gmail.com on 6 Jan 2009 at 2:46

Attachments:

GoogleCodeExporter commented 9 years ago 
Very good analysis.  I also noticed this behaviour except, after opening and 
closing 
PMS one additional time after the problem occurs, it seems to recover.  Same 
version 
but on Vista, 100% wired connections.

Original comment by jjwatmys...@gmail.com on 6 Jan 2009 at 3:00

GoogleCodeExporter commented 9 years ago 
Unfortunately that doesn't work for me (it was one of the first things I tried) 
:\

Original comment by meskibob@gmail.com on 6 Jan 2009 at 4:41

GoogleCodeExporter commented 9 years ago 
I have the exact same issue with the same setup: PC <-(Wireless G)-> Router 
<-(Wired 
Ethernet)-> PS3
I have port 5001 open in my router (DIR-655)

I have discovered that if I uninstall PMS and reinstall it, the PS3 will reply 
directly, but after closing PMS and restarting it the PS3 will not respond, 
this is all I get in Traces:
"[main] TRACE 22:14:15.453 Starting Java PS3 Media Server v1.02.1"
And then nothing.

Reinstalling PMS will make it work, but there must be some other way?

Original comment by johan.ku...@telia.com on 8 Jan 2009 at 9:20

GoogleCodeExporter commented 9 years ago 
Same issue here, setup: PC <-(Wired 100 Mbps)-> Router <-(Wired 
100 Mbps)-> PS3

Running Vista 32, router DLink DIR-635.

It always works the first time after installation and then no more, only way to 
get 
it running again is to uninstall --> install.

No connection problems at all with previous version 1.01

Original comment by jsela...@gmail.com on 8 Jan 2009 at 10:39

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I just tried to run PMS in admin mode and that did it for me, found the PS3 
directly.

After that i changed security properties for "Program\PS3 Media Server" folder 
to 
full access for the user account and that worked better, so you can get rid of 
the 
run in admin mode.

Original comment by jsela...@gmail.com on 8 Jan 2009 at 10:55

GoogleCodeExporter commented 9 years ago 
Hmmm, I have a D-Link 624... Could this be related to the router?

Original comment by meskibob@gmail.com on 8 Jan 2009 at 10:56

GoogleCodeExporter commented 9 years ago 
Had the same issue, thought I was going mad... :)

Jselande's solution solved it for me.  Good spot!

Original comment by JJKris...@gmail.com on 9 Jan 2009 at 12:53

GoogleCodeExporter commented 9 years ago 
Yeah, same happens with me - my debug.log is attached to issue 135 (which I saw 
first).

Only reinstalling PMS after it is shut down for the first time makes it work 
again.

Thanks

Original comment by ad...@radarhost.com on 10 Jan 2009 at 2:00

GoogleCodeExporter commented 9 years ago 
This is really weird as if I run v1.00 it connects all the time without issue 
but 
the new version only connects immediately after install / reinstall and then 
after 
this it will not connect again, even with a reboot unless I give it 
administrator 
privileges. At least there is a work around for now.

Original comment by simonjoh...@gmail.com on 10 Jan 2009 at 3:04

GoogleCodeExporter commented 9 years ago 
Maybe you guys are having a different issue than mine, as I'm able to reconnect 
on
restart and I'm the only user/admin, so all of my folders already have admin
permissions.  Should this be split into two separate issues?

Original comment by meskibob@gmail.com on 10 Jan 2009 at 3:10

GoogleCodeExporter commented 9 years ago

Original comment by ps3mediaserver@gmail.com on 11 Jan 2009 at 2:37

GoogleCodeExporter commented 9 years ago 
Huh.  Same here, Vista 32bit.  Set to run as service.  Works only once, then no 
more.
 1.0 ran just fine, so its a new bug.

Original comment by andydumi...@gmail.com on 11 Jan 2009 at 8:00

GoogleCodeExporter commented 9 years ago 
Running as administrator (right click option) is a work around for this.

Original comment by simonjoh...@gmail.com on 11 Jan 2009 at 8:02

GoogleCodeExporter commented 9 years ago 
"Set to run as service.  Works only once, then no more. 1.0 ran just fine, so 
its a 
new bug."

you have run an 1.0 as a service ? :)

Original comment by ps3mediaserver@gmail.com on 11 Jan 2009 at 8:26

GoogleCodeExporter commented 9 years ago 
anyway, please move into the 135, as the 104 has nothing to do with vista user 
rights

Original comment by ps3mediaserver@gmail.com on 11 Jan 2009 at 8:26

GoogleCodeExporter commented 9 years ago

Original comment by ps3mediaserver@gmail.com on 11 Jan 2009 at 8:45

GoogleCodeExporter commented 9 years ago 
One more thing I forgot to mention at the beginning:
TVersity works fine after restart a program restart, so I'm thinking this has 
to do
with how PMS closes the network connections and announcements.

Original comment by meskibob@gmail.com on 17 Jan 2009 at 3:59

GoogleCodeExporter commented 9 years ago 
Update:
1)with v1.04, forcing a different port is no longer a successful work-around
2)I'm not sure why I didn't do this before, but I tried pinging the PS3.  I 
always
get "Destination host unreachable" unless I have an active PMS connection open 
with
the PS3, and then it pings like normal.

Original comment by meskibob@gmail.com on 8 Feb 2009 at 10:52

GoogleCodeExporter commented 9 years ago 
Number 2) sounds like a firewall feature of the PS3, i.e. it'll reject random 
network
traffic until it has a media connection with a device?

Original comment by pete.hu...@gmail.com on 9 Feb 2009 at 11:31

GoogleCodeExporter commented 9 years ago 
This suggests that you can ping the PS3 ...
http://www.neowin.net/forum/index.php?showtopic=615702

Original comment by meskibob@gmail.com on 9 Feb 2009 at 12:49

GoogleCodeExporter commented 9 years ago 
It suggests you CAN, but also indicates that there's a problem in certain
circumstances. Since they reached no resolution there, can't be certain what the
problem is. Could perhaps be Windows firewall rather than the PS3, are you able 
to
ping other devices on your network?

Original comment by pete.hu...@gmail.com on 9 Feb 2009 at 4:00

GoogleCodeExporter commented 9 years ago 
Don't really have any other devices on the network... The only thing I could 
test is 
the PSP, but that may have the exact same issue as the PS3.  I guess I'll try 
when I 
get home from work.  I guess one other possibility is that I've enabled 
WAN-side 
ping blocking in my router, but it may be messed up and disabling ping on the 
LAN as 
well, although that should disable it even when I have the active PMS 
connection 
open.  Windows firewall is disabled as I use Symantec; I guess I'll try pinging 
with 
it disabled.

Regarding the neowin article and the checks in there: both the PC and PS3 are 
under 
the same gateway and subnet mask.  They get their IPs dynamically, but I've set 
the 
router to statically assign them through DHCP by MAC address.

Original comment by meskibob@gmail.com on 9 Feb 2009 at 6:59

GoogleCodeExporter commented 9 years ago 
I temporarily disabled Symantec and was able to ping the PS3 no problem.  Was 
stupid
and forgot to add the PS3 IP to the trusted networked IPs.  Unfortunately,
enabling/disabling Symantec had no effect on PMS working after a restart. :(

Original comment by meskibob@gmail.com on 9 Feb 2009 at 10:48

GoogleCodeExporter commented 9 years ago 
Edit.... or maybe it did.  Did a system restart and now everything seems to be
working hunky-dory with the new Symantec rule.  I'll give it some more time, 
see if
it comes back.

Original comment by meskibob@gmail.com on 9 Feb 2009 at 10:51

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
After quite a bit of testing, it seems this was the issue.  I can now turn on 
the PS3
and have PMS show up right away when it's already running.  Restarting PMS now 
works
fine. :)
I'm still a little curious as to why it worked in the first place though...
Anyways, I guess this can be issue can be closed.  Thanks pete.hurst for 
pointing me
in the right direction.

Original comment by meskibob@gmail.com on 10 Feb 2009 at 1:20

GoogleCodeExporter commented 9 years ago

Original comment by robinmul...@gmail.com on 20 Jul 2009 at 8:10