Router Simply Won't Recognize PS2 - ughhh

[BoboBlockSheep]

I've been working on this one for hours, and I've scoured the Googles and searched the forums, but to no avail.

First thing's first: I've got my router (WRT54G rev3.0 running Tomato v1.28 CFW). It's connected to my fat ps2 (30001) via straightway Ethernet cat5 cable. The ps2 is running FCMB v1.8 with the latest uLaunchELF. It was installed 100% properly, I assure you, through the noobie package no less.

Router/gateway is at 192.168.1.1, and subnet mask is ofc 255.255.255.0. In uLaunchELF I set up the network settings properly, and I've set the IP as something within the router's DHCP auto assign range and outside of it (192.168.1.100 - 192.168.1.149).

I start the networking component of uLaunchELF, and it looks dandy on its end. My router simply won't list the ps2 as a device, however. The only thing I could have imagined interfering with this setup is DHCP, so I turned it off but to no avail. The ps2 is not otherwise pingable or accessible. In fact, if someone told me that the Ethernet port on the ps2 is dead, I'd have no problem believing that at this point. I've restarted the router and the ps2 multiple times during this series of adjustments and tunings.

I haven't tried a direct computer <-> PS2 hookup for I don't have a crossover cable (or the components to make my own). I don't know how to find the MAC address of the ps2, especially because the guy I bought it from included the case for the network disc, but failed to actually provide the disc, so manual assignment is seemingly not possible atm.

If anybody has a clue I'd be much obliged.

[SP193]

I've been working on this one for hours, and I've scoured the Googles and searched the forums, but to no avail.

First thing's first: I've got my router (WRT54G rev3.0 running Tomato v1.28 CFW). It's connected to my fat ps2 (30001) via straightway Ethernet cat5 cable. The ps2 is running FCMB v1.8 with the latest uLaunchELF. It was installed 100% properly, I assure you, through the noobie package no less.

Router/gateway is at 192.168.1.1, and subnet mask is ofc 255.255.255.0. In uLaunchELF I set up the network settings properly, and I've set the IP as something within the router's DHCP auto assign range and outside of it (192.168.1.100 - 192.168.1.149).

I start the networking component of uLaunchELF, and it looks dandy on its end. My router simply won't list the ps2 as a device, however. The only thing I could have imagined interfering with this setup is DHCP, so I turned it off but to no avail. The ps2 is not otherwise pingable or accessible. In fact, if someone told me that the Ethernet port on the ps2 is dead, I'd have no problem believing that at this point. I've restarted the router and the ps2 multiple times during this series of adjustments and tunings.

I haven't tried a direct computer <-> PS2 hookup for I don't have a crossover cable (or the components to make my own). I don't know how to find the MAC address of the ps2, especially because the guy I bought it from included the case for the network disc, but failed to actually provide the disc, so manual assignment is seemingly not possible atm.

If anybody has a clue I'd be much obliged.

Which program were you running on your PS2 as you attempted to ping it?

If it is a program that does not control the Network Adaptor (Or does use the NA, but just did not initialize the network adaptor), pinging the console will not work.

uLaunchELF does not load the NA drivers unless you access a part of uLaunchELF that uses the NA.

Does the router reflect that the console is physically connected to it (E.g. the LINK light for the port that the console is connected to lights up)?

The network adaptor setup disc is not useful for homebrew software. It is only used for Sony-licensed software.
If you want to configure the NA for use with homebrew software, use a program like uLaunchELF or OPL to do that, or edit IPCONFIG.dat on your own if you know how to.

[BoboBlockSheep]

I tried ping from the command prompt on two different computers (WinXP laptop, Win7 desktop). I also tried nbtstat -a <ipaddress> from the win7 desktop. Ps2net was running as I tried to do this to use the FTP server (or host, which I'm aware of). Also, aside from pinging, I did try to forcibly go ahead and connect to what should have been the ftp address (i.e. ftp :// yadda)

The router acknowledges physically that something is connected to it, and the corresponding port LED does light up. But, of course, the device list shows nothing. I'll also note that tomato keeps logs, and there isn't any mention of a relevant device that would signify my ps2 trying to connect to the router.

Thus far everything I've tried to do was through uLaunchELF. Hopefully (key word) tomorrow I'll have a basic 4-port switch to use for testing purposes. If it works then I'll know for sure the problem is the router (specifically Tomato itself) and I can go bother those people about this since they should know how their own firmware works. But until then, I'm stuck.