PS2 Connected to Home Network - Help

[Skyline0964]

I have been trying to get my ps2 to successfully connect to my PC via crossover cable for the use of SMS and OPL. I have two ethernet ports, one is integrated into the motherboard and the other is in the PCI express slot. The crossover is running from my PC to the ps2, then I have a 50ft cat-5 ethernet cord running from my PC to the router. It doesn't matter what I try, everything fails. I can not get a successful ping from my ps2

PS2
IP: 196.70.2.22
Subnet Mask: 255.255.255.0
Default Gateway: 196.70.2.1

PC
IP: 196.70.2.19
Subnet Mask: 255.255.255.0
Default Gateway: 196.70.2.1



What does the IP address refer to, PS2 IP? PC IP? Everyone claims to put it as 192.168.0.2

[dlanor]

I have been trying to get my ps2 to successfully connect to my PC via crossover cable for the use of SMS and OPL. I have two ethernet ports, one is integrated into the motherboard and the other is in the PCI express slot. The crossover is running from my PC to the ps2, then I have a 50ft cat-5 ethernet cord running from my PC to the router. It doesn't matter what I try, everything fails. I can not get a successful ping from my ps2

PS2
IP: 196.70.2.22
Subnet Mask: 255.255.255.0
Default Gateway: 196.70.2.1

PC
IP: 196.70.2.19
Subnet Mask: 255.255.255.0
Default Gateway: 196.70.2.1

The problem is evident.

The PC address you specify, and the default Gateway, are the IP addresses of the other PC port (to which the PS2 is not connected) and of the router that port is connected to.

So the PS2 attempts to send packets using the router as 'gateway', though it is not connected to the router. And considering the info given in your other pictures it is also clear that you have configured the PS2 to use the same IP address for its own LAN port as is also used for the secondary port of the PC, to which it is connected.

What does the IP address refer to, PS2 IP? PC IP? Everyone claims to put it as 192.168.0.2

No they don't. And anyone who does state that as a mandatory value is dead wrong.

It is just a 'possible' value, which fits within the commonly used '192.168.0.x' subnet set up by default for most routers when bought as new. So it is a suitable example for most people. But if you use a different local subnet with your router, such as '196.70.2.x' then all units connected to that router should also have IPs fitting within that same subnet spec (except for the WAN port of course).

The IP address shown in this picture is the IP address of your PC on the subnet connection achieved by the network port for which this property sheet applies.

Possibly you don't quite grasp the fact that your PC does not have just one IP address.

It has one IP address for each LAN port it uses, so a different IP address for each subnet to which it has a direct connection. And all addresses on all subnets must be unique, just like the subnet ranges must be unique. Otherwise the routing is indeterminate.

Assuming that this is the secondary LAN port you use for connecting the PS2, then that IP address (above shown as '192.70.2.22') would be the one that you should configure OPL to use for contacting the PC server. But this is doomed to failure if you do not also change the IP address of the PS2 LAN port, since you've already stated that this also uses '192.70.2.22' so that it conflicts with the IP address of the PC.

And it is really an error to specify the same subnet range for two different ports of your PC. Standard routing rules may then send packets to the wrong port. And in all cases it is a grave error, preventing all traffic, to have two units connected to each other and using the SAME IP address.


What I would do:
If you have any spare ports in the router, then simply skip using that extra LAN port of the PC and instead connect the PS2 LAN port to one of the free ports in the router, and configure OPL to use exactly what you already stated doing, EXCEPT for the PS2 IP address, which should be changed to something else within the same subnet range which does not conflict with any existing LAN port on your PC or any other equipment connected to your router.

You could even keep the PS2 IP address as '192.70.2.22' as long as you remove that IP definition from the secondary LAN port of the PC, and/or disable that one completely.

If you really don't have any spare ports in the router, then you may need to use the secondary LAN port after all, though differently configured, so as not to conflict with your primary subnet. But we can cross that bridge when we come to it. (Meaning if/when you say that your router is already 'full' with no free ports remaining.)


Edit: I just noted your mention of a 50 feet cable to the router, so using a router cable for the PS2 as well is probably not a feasible option. so what you should then do is to change the IP address of the secondary LAN port of the PC, as well as of the PS2 so that they use a different subnet range as well as unique addresses.

Here is one example of how to do that...

----- Start of OPL's 'Network config' -----
- PS2 -
IP 192.168.10.10
Mask 255.255.255.0
Gateway 192.168.10.1

- PC -
IP 192.168.10.1
Port 445
share PS2SMB
User your_PC_username_here
Password your_PC_password_here
----- End of OPL's 'Network config' -----
Make sure settings are saved properly before you turn off the PS2.
Then do that restart with the new configuration.

Naturally you also need to reconfigure the secondary LAN port of the PC accordingly:
IP address: 192.168.10.1
Subnet mask: 255.255.255.0
Default gateway: 192.168.10.10 (Or just leave it unset)

This way all subnets and addresses are unique, as required for proper routing.

Btw:
There is near infinite variation possible on the example I gave here, all of which would work fine. The numbers themselves are not really important, as long as each unit has what the other expects and without any routing conflicts.

Best regards: dlanor

[Skyline0964]

thanks for the help but i got it to work I bridged the connections and set it to

PS2
ip 196.70.2.22
mask 255.255.255.0
gw 196.70.2.1

pc
196.70.2.23
port 445
share name SKYLINE0964

I also got SMS to work on smb server :P