The above video goes away if you are a member and logged in, so log in now!
Open PS2 Loader randomly freezes on 1
Open PS2 Loader randomly freezes on 1 –
I'm out of ideas what could possibly be the problem.Whatever I try and it works,the next time when I try the app it freezes on 1 without changing any settings.
When it's going to work,the connection is maded by less than 5 seconds.
Here's the a dump from Wireshark.There are two files,one when it works and one when it freezes.
That is what I reported on the main thread
At least I'm not the only one ... so my proposition could be accepted
Ah, I got another one. Since the new initialization procedure of network (the both "commented" as "hacky" ), it freeze half the time (on "initialization network 1"). I just have to poweroff the PS2, and start over again ... sometimes I have to try 3 times, and some other it just start the first one.
What are these "tcp port" ? Maybe you could put an option in the network settings like "standard init / fast init". The standard would use the old (slower but more compatible) method, and the fast will use the new one ?
Yes,I forgot that you have the same problem(I didn't fully understand it at first because the SMB wasn't working at all for me before).
Guess we are on the same boat...what could possible be,starting whenever it feels like it
The windows side gets confused by a new connection thinking it is a malformed packet from old connection. It demands reset (RST) of the communication. TCP on PS2 side retries the connection ignoring the RST from windows (I presume because it thinks it is misplaced RST?) using a different port.
My humble opinion follows : This is a situation where the port randomization could actually hurt. The new connection effort should be led on the same source port after RST is received - I think that this would mean TCP on the windows side would not get confused by the ill-placed connection attempts.
The cause of all this is sems to be an unclosed SMB connection after a PS2 reset.
So couldn't the PS2 first sent a "close" packet at start in everycase, without bothering the answer.
That would reset an eventual previous unclosed connection
That's exactly what I thought it is and that's why I tried with TCPView to close the connections but it didn't fully close them.
Originally Posted by volca
So what exactly do you suggest...to allow only 445 TCP port from the settings of my second card?
If it's that then I already tried this but it was the same...it freezes randomly.
I had similar problems before when I used RadHost Client on SMS and Ule and that's why I switched to PS2CLient(I wasn't able to connect because of unclosed connection)
This may work - but - we would have to somehow deduce the last port,syn and ack values (not sure if all those, but at least some) and those likely don't survive reset.
Originally Posted by Gilgamesh88
If reset button handling could be hooked to terminate the connection before reset happens, that may help... Jimmi implemented connection closing on IOP reset but maybe it does not always fire - not sure.
It is hard for me to suggest anything at this point. My knowledge of TCP is still kind of shallow.
The question is why some people don't have any problems and the connection is always successful and for the other it's real pain to make it work.
This most likely isn't ops2l fault.
I encounter the connection problem as well - but not in the rate that would cause it to be a bigger obstacle in usage. Still I'd like to eliminate it
I loose all the desire to play using SMB till I make it work.I don't know what else to try.