ps3netsrv from mmCM release doesn't work at all for me !

[coveman]

There is ONLY ONE ps3netsrv.exe version (there may be different GUIs but that's not important).

ps3netsrv.exe - 20 480 bytes. I hope you don't confuse it with the old one for older mm versions (which is named ps3serv.exe and is 52 224 bytes)

ps3netsrv.exe will always respond with:

Connection from X.Y.A.B

no matter if your PS3 connects or you succeeded with telnet.

For example I just connected via telnet and pressed [ENTER] 8 times and the telnet console closed:

Code: Select all

D:\PS3_ROOT>ps3netsrv.exe . 11222
Waiting for client...
Connection from 127.0.0.1


[dlanor]

How improper can it be when FTP and UPNP work perfectly between the same two machines...?
So I really don't think it "all comes to" my basic network setup. There has to be more to it.

You confuse both.

No I don't. You are just too quick to draw that conclusion.
I never stated that each of the cases were identical, but only that they showed basic network setup as working.

Accessing your PS3 via FTP may work just fine, because the PS3 acts as a SERVER (and your PC is a CLIENT).

Yes, so for the FTP case we have connection established from PC to a PS3 server.
And with the UPNP case of the PS3 media server we have connection established from PS3 to a PC server.
Thus the network is shown as working for server connections both ways.

With /net_host (ps3netsrv) your PC acts as SERVER and your PS3 is a client.

Which is similar to the case with the media server.
Not that there is any real difference in how the network sends server replies as compared to how it sends connection requests.

It all comes down to basic IP packets sent both ways for both usages.
Mostly TCP/IP for the main traffic, interspersed with some UDP/IP and ICMP stuff too.

And since no firewall or router blocks interfere in any way with any packets sent between this PC and PS3 pair, the ability for any client to send packets to a server at the other end and get replies back does in fact prove the basic functionality of this network.

If you can't connect to the ps3netsrv PC on the port you used from another PC - then the PS3 won't connect to it ever, too.

That's true of course, so the telnet method is definitely worth trying.

I appreciate that you are trying to lead me to a solution here, and I am grateful for that, but please don't assume that i have no clue to basic networking, as I've had some experience in using and programming network stuff for quite a long time.

There is ONLY ONE ps3netsrv.exe version (there may be different GUIs but that's not important).

ps3netsrv.exe - 20 480 bytes. I hope you don't confuse it with the old one for older mm versions (which is named ps3serv.exe and is 52 224 bytes)

No, both the 'versions' were taken from two different recent mmCM release packages. But there may have been some mixup in windrider's testing, as one of them refused to show responses. (perhaps a previous 'invisible' process instance stole the traffic).

ps3netsrv.exe will always respond with:

Connection from X.Y.A.B

no matter if your PS3 connects or you succeeded with telnet.

That sounds good, as I do need feedback on the testing, but it still contradicts what windrider said, about how nothing was displayed even when the transfers were in fact working. I'll just have to test it myself of course (instead of sitting here typing posts... )

I just made such a test from one of my other PCs, and the ps3netsrv program on the main PC did respond as you described, so that connection is proven. So the big question remains: "Why doesn't my mmCM ever connect to this server, when properly configured to do so ?"

Best regards: dlanor

[coveman]

Then verify again if you have the IP and PORT of your main PC set properly in mmCM.

When you click the "/net_host0 - Enable" in [Settings -> Network Servers] you get your IP without the last octet -> [192.168.10.] Enter the last octet (64 in your case) and press [START] twice. Then you'll be prompted for port - press [START] to accept the default 38008.

If all goes well you should see a blue-disc with network sign + rotating arrow in one of the corners of the PS3 screen.

If it doesn't work - I really don't know what else to suggest.

As a final resort - exit to XMB and go to Network Settings and check again if your PS3 IP is set properly (in the same subnet) and that you at least have proper subnet mask entered (although all should be ok there since you can use FTP and UPNP).

[windrider]

There is ONLY ONE ps3netsrv.exe version (there may be different GUIs but that's not important).

ps3netsrv.exe - 20 480 bytes. I hope you don't confuse it with the old one for older mm versions (which is named ps3serv.exe and is 52 224 bytes)

No, both the 'versions' were taken from two different recent mmCM release packages. But there may have been some mixup in windrider's testing, as one of them refused to show responses. (perhaps a previous 'invisible' process instance stole the traffic).

ps3netsrv.exe will always respond with:

Connection from X.Y.A.B

no matter if your PS3 connects or you succeeded with telnet.

That sounds good, as I do need feedback on the testing, but it still contradicts what windrider said, about how nothing was displayed even when the transfers were in fact working. I'll just have to test it myself of course (instead of sitting here typing posts... )

I just made such a test from one of my other PCs, and the ps3netsrv program on the main PC did respond as you described, so that connection is proven. So the big question remains: "Why doesn't my mmCM ever connect to this server, when properly configured to do so ?"

Best regards: dlanor

Basically my point about the the ps3netsrv from mmCM 4.01 compared to 4.02 at least shows the connection as I pictured.
So when first trying the ps3netsrv from mmCM 4.02 (although the same, just different gui) I could not see if I was connected.
Now this is in Windows XP Pro

Yet on Windows 7 , using the ps3netsrv.gui from mmCM 4.02, I can see the connection.

[dlanor]

Sorry for 'dropping the ball' on this thread, but when last I tried to post a follow-up on it here the site seemed to crash, and I was unable to connect to it again for quite a while. And 'naturally' this happened when trying to submit a large post explaining (in part) what had happened and how I resolved the problem... I tried a few more times since then, but still couldn't get connected, so then I dropped the whole matter to get busy with other stuff (until today that is).

As stated before I had double and triple checked the correctness of the IP addresses and the port numbers both at PC and PS3 ends of the connection, and I had also reconfigured that data over and over again in attempts to make it work, without any noticeable effect. But in one of my final attempts at this I created a second PC host server configuration entry in mmCM, with identical address and port values as the old one, and suddenly mmCM started responding to connections from the client on my PC, so I saw my first connection responses in the PC command window. But real data transfers still failed with corruption... (possibly due to some conflict between the two semi-identical server entries)

But when I removed the old server entry, so that the new entry remained alone, everything started working quite well.
So for all practical purposes the issue is resolved, leaving only some big question marks as to what really happened during the failures...

To me those failures mean that some internal difference in the configuration data, invisible to the user, must have 'contaminated' the older entry, since that was fully identical to the new one in all visible respects, but did not give the same results. Possibly some update of mmCM changed the use of some 'internal' configuration flag or other value, in some way not affected by editing an old entry in the new GUI, and preventing that old entry from working. This could explain why a newly created entry worked differently from my old entry, though both are identical in all visible respects.

In any case, this is not a problem likely to recur, so it's not really worth spending more time to investigate it.

Also, after testing it for a while (once I had it working), I soon decided that it's not a very practical way of doing things. At least not for me. Not only does it require running a separate command-line server on the PC, but the mmCM file manager GUI offers less convenient methods of navigation and mass file processing, as compared to using FTP and a good FTP client like FileZilla, with which I can just drag-drop any collection of files and folders I want copied between the current FTP client directory and any Windows Explorer directory window, in either direction. This ability combined with FileZilla's convenient FTP bookmarks allows a level of usage convenience that the mmCM file manager can never even approach. So I'll be sticking to FTP for networked PS3 transfers in future.

(Btw: I do realize that the same limitations also apply to the "host:" server as implemented in uLE, but that case is still different as its FTP server is less reliable/speedy. So with the PS2 I still prefer "host:" rather than FTP.)

Best regards: Ronald Andersson (aka: dlanor)

[windrider]

Thanks for the update dlanor. I was wondering how you were making in out in testing ps3netsrv using Windows Xp Pro and your PS3

At least you got too test it out, and find whether you would like to use it or not.. I must agree, I would rather FTP than bother with it myself.

I don't really care to play games or watch videos over the network. I already have a couple USB drives devoted to that. One for games, emulators, and One for my Videos. I did however try it, just too see.

Well if you did want something changed with mmCM, then just post in our Features/Request thread and anything is possible.