Forum: PS2 General Discussion - PlayStation 2 console talk covering subjects like saving PSX games to your PS2 memory card, what speeds to burn PS2 discs or find out answers to many other general PS2 questions.


The above video goes away if you are a member and logged in, so log in now!




 
Would you like to get all the new info from
PSX-Scene in your email each day?




Want to learn more about the team keeping you up to date with the latest scene news?

Read about them now!

Check out our Developer bios, too!

 


User Tag List

Thread: Networks, Crossovers, Conflicts, and other Nasty Stuff
  

Results 1 to 7 of 7
  1. #1 Networks, Crossovers, Conflicts, and other Nasty Stuff 
    Cliffjumper's Avatar
    Cliffjumper is offline -- Autobot --
    Join Date
    Jun 2003
    Location
    Arkansas, USA
    Posts
    50
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Hey, I was wondering if I could get some help with Inlink and Pukklink. I've got it working just fine on my system at home, and here's my setup:

    Computer ------- Router --------- PS2
    (with all straight-through patch cables)

    Everything works just fine, using the default IP settings.

    However, I run into a lot of problems getting a Pukklink setup to work at my friend's house. He's got kind of an interesting setup. I'm trying to get it to connect to his XP laptop, which has a standard ethernet port, but is also on his wireless network.

    1) I think I've got the crossover cable crimped properly, like this, right?
    1 -> 3
    2 -> 6
    3 -> 1
    6 -> 2

    2) I've tried getting it to connect after disabling the wireless network card, just to be sure that there weren't any IP conflicts.

    3) It's the same PS2, same network adapter, same versions of Pukklink and InLink that I've used successfully at home.

    Could someone tell me what IP addresses I should use in the config to get things working smoothly? What IP addys should I be looking at in WinXP's ipconfig?

    Thanks a million for any help.
    Reply With Quote  

  2. #2 Re: Networks, Crossovers, Conflicts, and other Nasty Stuff 
    Da Brass's Avatar
    Da Brass is offline やっろか?
    Join Date
    Sep 2002
    Posts
    999
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Originally posted by Cliffjumper
    Hey, I was wondering if I could get some help with Inlink and Pukklink. I've got it working just fine on my system at home, and here's my setup:

    Computer ------- Router --------- PS2
    (with all straight-through patch cables)

    Everything works just fine, using the default IP settings.

    However, I run into a lot of problems getting a Pukklink setup to work at my friend's house. He's got kind of an interesting setup. I'm trying to get it to connect to his XP laptop, which has a standard ethernet port, but is also on his wireless network.

    1) I think I've got the crossover cable crimped properly, like this, right?
    1 -> 3
    2 -> 6
    3 -> 1
    6 -> 2

    2) I've tried getting it to connect after disabling the wireless network card, just to be sure that there weren't any IP conflicts.

    3) It's the same PS2, same network adapter, same versions of Pukklink and InLink that I've used successfully at home.

    Could someone tell me what IP addresses I should use in the config to get things working smoothly? What IP addys should I be looking at in WinXP's ipconfig?

    Thanks a million for any help.
    2 and 6 are the only wires you need to have the crosstalk. The wires are counted with the top of the RJ-45 plug facing you (with the copper pins).

    Set the XP laptop IP as 192.168.25.1, netmask 255.255.255.0, Gateway as blank.

    PS2 should have same settings, except IP is 192.168.25.X where X is anything other than 1 and up to 254, Gateway is set as the IP of the XP Laptop.
    USA v9 SCPH-50010 Datecode 3C and USA Network Adapter
    JAP v0 SCPH-10000 with v1.00 Utility Disk and JAP External 40GB HDD BB Unit
    w/ Tray Switch

    http://www.playstation.jp/psbb/img2/ps2_2.jpg
    Reply With Quote  

  3. #3  
    cola is offline Member
    Join Date
    Sep 2003
    Location
    Detroit what?
    Posts
    39
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Uh actually when setting it up you want it to be 50 or below. I contacted Linksys about it a while back when I was configuring it. Something like 51-254 were Dynamic and 1-50 were static. I set my ps2 as 192.168.1.50 and it works fine.
    Reply With Quote  

  4. #4  
    RAISTLIN's Avatar
    RAISTLIN is offline Oh, you're my bitch now!
    Join Date
    Jul 2002
    Location
    B.F. Egypt, SC, USA
    Posts
    848
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    The wiring you listed is "technically" correct. Diagrams and good how-to posted here:

    http://duxcw.com/digest/Howto/network/cable/cable5.htm

    I always start with white/green then go to the orange set for consistency. All you do is just swap the orang/green postions on the other plug. This way I can quickly ID my crossovers by finding the orange wires in first position. Some guys will opt to use the blue and brown sets for xovers, orange/green sets for straight throughs which really makes them stand-out.

    Raist
    If it ain't broke don't try to fix it! But, hell if you can tweak that bastard just a little bit more....hehehe.
    Reply With Quote  

  5. #5  
    Szwaba67 Guest
    Originally posted by cola
    Uh actually when setting it up you want it to be 50 or below. I contacted Linksys about it a while back when I was configuring it. Something like 51-254 were Dynamic and 1-50 were static. I set my ps2 as 192.168.1.50 and it works fine.
    That's only true for the particular settings of your Linksys router. Your DHCP server in the router is most likely set to deal out IPs higher than 50. That's why they told you 1 through 50 were static. If there's no DHCP server then there aren't any dynamic IPs.
    Reply With Quote  

  6. #6  
    nightcrawler is offline Member
    Join Date
    Oct 2002
    Posts
    63
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Crossover is corrected as everyone else is saying.

    I think the problm is the IP address since there is no DHCP server on a crossover setup. you need to assign say 192.168.1.2 for xp and 192.168.1.3 for PS2 both with netmask 255.255.255.0. The real IP dose not matter as long as they are not the same and they are on the same subnet. Gateway dose not matter, it's not used when it is on the same subnet. but put 192.168.1.1 if you have to put donwn something.

    another way is to turn on the ICS on the wireless and share it to the ethernet interface. that way, XP will set the ethenet to
    192.168.0.1/24 gateway:192.168.0.1 and act as a DHCP server and router.
    PS2: NTSC 39001 V7 + Messiah 2
    Reply With Quote  

  7. #7  
    Cliffjumper's Avatar
    Cliffjumper is offline -- Autobot --
    Join Date
    Jun 2003
    Location
    Arkansas, USA
    Posts
    50
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Hey everyone, thanks for all the input. Yours especially Nightcrawler, turning on ICS really seems like it'd work. I'm gonna try it this weekend, I'll post the results. Oh, and Raist, thanks for the wiring diagram. I'll be a little more confident in the wiring now.
    Reply With Quote  

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •