Guest

Cisco Small Business Voice Gateways and ATAs (Linksys Business Series)

Setting-Up a PlayStation®2 with a Linksys VOIP Router


Document ID: 108670


Contents

Introduction
How do I set-up my PlayStationregTag;2 with my Linksys VOIP router?
Related Information

Introduction


This article is one in a series to assist in the setup, troubleshooting, and maintenance of Cisco Small Business products (formerly Linksys Business Series).

Q. How do I set-up my PlayStationregTag;2 with my Linksys VOIP router?

A.

Note: Before proceeding please take note that Linksys does NOT support the configuration of PlayStationregTag;2. The following instructions simply tell you how to configure the router for the PlayStationregTag;2, not the game console itself. For technical support on the PS2regTag;, contact Sony.

In setting-up a PlaystationregTag;2 on the Linksys router, you will need to perform two steps:

  1. Setting-Up the PlaystationregTag; 2
  2. Configuring the Router

Setting-Up the PlayStationregTag;2

Step 1:
After installing your PlayStationregTag;2 Network Adapter, connect a regular straight thru cable from one of the numbered ports on the router. Plug the other end of the cable into the PlayStationregTag;2's Network Adapters Ethernet port.

Step 2:
You must assign a static IP address on PlayStationregTag;2. To do that, please consult your PlayStationregTag;2 documentation, or click here. In this example "192.168.15.20" was used for the IP Address, "255.255.255.0" for the Subnet mask, "192.168.15.1" for the Default Gateway, and your DNS information.

Once the PlayStationregTag;2 is set-up, configure the Linksys router by following the instructions below.

Configuring the Router

Step 1:
Access the router's web-based setup page. For instructions, click here.

Step 2:
When the router's web-based setup page appears, click Applications and Gaming and then click DMZ.

Step 3:
Select Enabled and enter the PlayStationregTag;2's IP address in the DMZ Host IP Address.

Step 4:

Click .

Related Information


Updated: Dec 12, 2008Document ID: 108670