Can't get FTP to connect...?

[MrCat]

Hi I'm new at this so bear with me please

I have a slim PS2 connected to my PC with a crossover cable. PC detects network connected.
PC IP 192.168.0.1 subnet 255.255.255.0
PS2 IP 192.168.0.10 subnet 255.255.255.0 gateway 192.168.0.1

In uLaunchELF I launch the network and it says FTP server starting etc, and then shows the IP at the top - but I can't ping from my PC at all.

No PC firewall. Cables working OK.
I'm beginning to think the PS2 has a hardware problem because it shouldn't be more complicated than this?

Any help appreciated!

[dlanor]

Hi I'm new at this so bear with me please

I have a slim PS2 connected to my PC with a crossover cable. PC detects network connected.
PC IP 192.168.0.1 subnet 255.255.255.0

No gateway ?
The TCP/IP properties of WinXP always include a gateway entry, so what are you using ?

PS2 IP 192.168.0.10 subnet 255.255.255.0 gateway 192.168.0.1

This looks fine to me.

In uLaunchELF I launch the network and it says FTP server starting etc, and then shows the IP at the top - but I can't ping from my PC at all.

After using the uLE command "MISC/PS2Net" to start the FTP server it should be replying to correctly addressed "ping" packets, as in the following sequence that I just copy-pasted from a WinXP command-line window:

D:\DL>ping ps2

Pinging PS2 [192.168.10.10] with 32 bytes of data:

Reply from 192.168.10.10: bytes=32 time<1ms TTL=128
Reply from 192.168.10.10: bytes=32 time<1ms TTL=128
Reply from 192.168.10.10: bytes=32 time<1ms TTL=128
Reply from 192.168.10.10: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.10.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

As you can see I use a slightly different subnet, and my setup is a little different as the ps2 is connected to the same router as my other LAN units, but even so you should get similar responses for your own crossover setup, when everything is working properly.

No PC firewall. Cables working OK.

Good, that is as it should be then.

I'm beginning to think the PS2 has a hardware problem because it shouldn't be more complicated than this?

I'm not sure, but I think it might be a problem if you never used the official network disc to initialize the use of this interface for the console. Doing this might help homebrew software like uLE to also gain access to it in future sessions. So if you never did that, it is something you ought to try.

Since all slim consoles have this interface, the network access disc is included with every console sold, so you should have one available (unless you bought the PS2 second-hand from someone who lost or broke the disc).

Best regards: dlanor

[MrCat]

Thanks for that dlanor.
I have had the PC's gateway set to my router address (same subnet), and also tried disconnecting from the router and not having a gateway - to further simplify matters. Router-PC-Playstation is the set up.
Ping gets no response at all - just a timeout - although the icons in the XP system tray and network properties say connected. Status for the connection says packets sent but 0 received.
What you suggest about the original setup (driver?) disc is interesting. I bought the PS2 second hand so I didn't know about that. It was newly refurbished with new lazer and MOD chip installed. Can I download the disc from somewhere do you think?

[dlanor]

Thanks for that dlanor.
I have had the PC's gateway set to my router address (same subnet), and also tried disconnecting from the router and not having a gateway - to further simplify matters. Router-PC-Playstation is the set up.

I assume that you really meant PC-Router-Playstation2, implying direct connection of the router both to PC and PS2, but no direct connection between PC and PS2, and (at this stage) nothing else connected in this LAN.

Ping gets no response at all - just a timeout - although the icons in the XP system tray and network properties say connected.

Those icons signify only that the hardware signal levels are in a valid state, so those show connection the moment you plug the wires into the router (with it turned on). But they don't mean that any traffic is passing to/from any other port on that router, as required to communicate with the PS2.

Status for the connection says packets sent but 0 received.

That was expected as nothing was received by the ping handler in your command line window either. Had real ping response packets arrived from the PS2 they would have appeared there as well.

What you suggest about the original setup (driver?) disc is interesting. I bought the PS2 second hand so I didn't know about that. It was newly refurbished with new lazer and MOD chip installed. Can I download the disc from somewhere do you think?

I'm not sure about our legal position on that. Since the disc is included with every slim PS2 sold, every owner of a slim PS2 is entitled to have it. But the software on it is still copyrighted by Sony, so the right of anyone else to distribute it is very dubious.

But since you are the legal owner of that PS2 now, you should feel no moral objections against trying to get hold of a copy of that disc if you can. I'm just not sure if we can help you with it, for legal reasons.

This site has to stay 100% legal, or we can expect Sony to squash us like a bug. They do have sufficient money to do that, as well as the inclination (they seem to hate all forms of homebrew work), so we can't give them any legal excuse to do it.

Best regards: dlanor

[MrCat]

Thanks again

I originally had the PC connected to router via wireless, and crossover cable from PC to PS2 with the connection bridged in Windows.
Tried various setups and got down to just PC to PS2 with no bridge and the wireless disabled - but still nothing. I even tried my laptop connected to PS2 with nothing else to complicate matters. It's like the PS2 just sits there refusing to talk for no obvious reason.

Trying to 'get hold' of a disc today, and I'll let you know if it solves my problem. It's a good idea and I have my fingers crossed!

[MrCat]

OK I've got the network disc running and all the settings correct, but it gets to diagnostics and says the cable is unplugged... when it's not. PC still saying connection (for what that's worth).
Looking more and more like a hardware fault do you think?

[dlanor]

OK I've got the network disc running and all the settings correct, but it gets to diagnostics and says the cable is unplugged... when it's not.

That is decidedly suspicious. At best it just means that a cable or cable connector is broken, but at worst it means that the PS2 port itself is broken (either the connector or the chip it connects to).

PC still saying connection (for what that's worth).

That info is worth exactly nothing, in either of two ways.

With a router it is worthless because it only tests the output voltages of the router, not of the PS2.

With crossover cable it is still worthless because even though it does test output voltages of the PS2 then, it does not test the PS2 inputs. (If PS2 inputs are broken, it never gets the requests from the PC, which explains why it never sends any reply packets.)

Looking more and more like a hardware fault do you think?

Yes, I'm afraid so.

Best regards: dlanor

[JoeUser38]

Hi I'm new at this so bear with me please

I have a slim PS2 connected to my PC with a crossover cable. PC detects network connected.
PC IP 192.168.0.1 subnet 255.255.255.0
PS2 IP 192.168.0.10 subnet 255.255.255.0 gateway 192.168.0.1

In uLaunchELF I launch the network and it says FTP server starting etc, and then shows the IP at the top - but I can't ping from my PC at all.

No PC firewall. Cables working OK.
I'm beginning to think the PS2 has a hardware problem because it shouldn't be more complicated than this?

Any help appreciated!

If I might ask, how do you know the cables are working ok? Did you try the same cable on another device successfully, or use a cable tester, or what?

[MrCat]

Thanks for your input JoeUser38.
I don't have a cable tester but I know this cable works fine when I connect other equipment together. I've also tried connecting the PS2 directly to the router with a straight through cable.
I even tried PS2 - PC with straight through rather than crossover in case the PS2 could compensate like a router does.

I'm wondering if maybe the modchip (Matrix Infinity) is know to have issues with interferring with a network...?