The above video goes away if you are a member and logged in, so log in now!
hdl_dumb error: no connection.. actively refused
hdl_dumb error: no connection.. actively refused –
I've had hdl_dumb/hdld_svr.elf 0.7.3 combo working as recently as a few weeks ago.
Now when I try to connect via network I get "the connection could not be made because the target machine actively refused it" almost immediately
I've also tried hdl_dumb/hdld_svr.elf 0.8.2, with duplicate results.
I can "ping" the ps2 with no problem. If I unplug the ps2 from the hub, I get "the connections attemp failed..." as proper.
I can use execftps and the network connect with ulaunch3.4i with no problems. They use the same ipconfig.dat as hdl_dumb does. Also inlink works fine.
The only devices connected to my hub are my main pc and the ps2.
I've tried other known working network cables anyway, and one of my kid's pc's, again same error.
I've also tried different launchers (ulaunch3.41i, launchelf 3.2b, ps2menu, keylaucher 0.5 b2 and previous versions)
Both pc's are Win XP, one home ed., one Pro. Turned off XP firewall (no 3rd party firewall installed)
I'm about to fireup an old win98 pc, (if hdl_dumb even runs on that) and try it. The only thing I can think of is some XP Service pack is causing a problem, but I would think others would be running into this if that were the case.
I'm thinking of capturing the packets too, to see exactly what the ps2 is coming back with.
Anyone got some more ideas? If not, i'll take the physically connect the drive and run hdl_dump (sigh)
PS2 v9. DMS 4 pro. 80GB western digital
Sheesh... After some more investigating, the HDD was not accessible at all anymore. It was as if there was no Hard drive in it!
My kids must have pulled it off the shelf this morning gave it good knock. I pulled off the network connector and the HDD was disconnected!
So, all is well.