[axeman61]

I've looked through every guide on the issue. I have DMZ and UPnP enabled on my router. I have the right ports forwarded (and I've checked with portforward.com's forwarding tool) to the PS3's IP Address.

TCP: 80,443,5223
UDP: 3478-3658. 3479's supposed to be listed, but I just made it a range between the other two numbers. I've already checked; listing the numbers like this isn't the problem.

I have my internet connection set to a static IP.

Despite all this, no matter what steps I take to remedy the situation, I still can't get NAT 2 on my PS3 connection.
My router is an Airnet Aer014. I'm starting to believe I can't get the connect because it seems to be crap. The only support I've found for this thing is its user manual (which doesn't list the manufacturer details or help with this situation) that came on a CD and the Portforward.com page on forwarding ports on it.
If you guys think the router is the problem, can you recommend me one I can get for 20-40 bucks?
Otherwise, if you have a solution or can point me in the right path, help would be much appreciated. My online on PSN isn't terrible, but it can disconnect from the network when I'm playing certain games. Also, I'm hearing that NAT 2 is almost like having the ethernet cord plugged right into the PS3 from the modem. I'd like that.

[moptix]

IF YOU WANT TO FIX YOUR NAT TYPE TRY THIS
http://manuals.playstation.net/docum...ctadvance.html

WHEN U GET TO IP SETTING GO TO PPPoe

[axeman61]

I've already tried that. And that looks outdated. I've never seen the DHCP page when I'm trying to tweak the settings.

[JohnWill]

What is the EXACT make and model of the modem you are connecting this router to?

[axeman61]

Speedstream 5360 Ethernet ADSL Modem from Efficient Networks.

If you need more info about the modem, I'll be glad to give it.

Oh wait, did I need to forward stuff in/make a static IP for my modem first before all of this?

Edit: there's a brand new problem that could have something to do with this.

Along the vein of what JohnWill was implying, I plugged my modem directly into the computer and tried to hookup to the internet through my old connection. I did it to perhaps surf my modem and change the settings within there. The internet still works, but I kept getting redirected to my ISP's help page. Apparently, the password within my modem I've been using to connect to the internet before getting a router is different from now. I remember a password change, but not the previous password. I'd call our ISP about this, but we're past due on our phone bill and the automated system won't let me get past without a payment. So that's on hold until tomorrow when a payment can be made.

However, surfing on the router is just fine. The router seems to have the current password. Isn't the modem the basic gateway to the internet? What's up?

Just letting you guys who actually want to help know of another problem that could be related to this.

[JohnWill]

I'd actually like to see this when connected directly to the modem without the router in the picture.



Hold the Windows key and press R, then type CMD to open a command prompt:

In the command prompt window that opens, type type the following command:

Note that there is a space before the /ALL, but there is NOT a space after the / in the following command.

IPCONFIG /ALL

Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard.
Paste the results in a message here.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.

[axeman61]

...>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : [censored]
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-11-11-9E-90-C8
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 68.94.156.1
68.94.157.1


Was I supposed to reboot the computer and do ipconfig, because that's the exact same readout as with the router.

[JohnWill]

You need to enable DHCP in order for us to see anything useful.

Select Start > Settings > Network Connections.

• Double-click the Connection icon of the connection you wish to modify to open the Connection Status window.
• Click the Properties button to open the Connection Properties window.
• Click to highlight Internet Protocol (TCP/IP).
• Click the Properties button to open the Internet Protocol (TCP/IP) Properties window.
• TCP/IP Properties window, IP Address tab
• Select Obtain an IP address automatically.
• Select Obtain DNS server address automatically.
• Click OK to return to the Local Area Connection Properties window.
• Click OK to return to the Network Connections window.

[axeman61]

OK, here it is again, with DHCP enabled, from the modem to the computer:


ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : [censored]
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-11-11-9E-90-C8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.216.234
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

[JohnWill]

Now you're not finding a DHCP server at all.


TCP/IP stack repair options for use with Windows XP with SP2/SP3.

Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands, each followed by the Enter key:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.

[axeman61]

Before I do that, what will that do? What am I supposed to do after that? Try ipconfig from the modem > computer connection again?

[JohnWill]

Yep, connect directly to the modem and do the IPCONFIG /ALL again.

[axeman61]

Sorry for the lateness. I talked with my ISP about resetting the modem password. They did it, and I was able to get online and surf with the modem. I then set the same password for the router. Everything's synchronized. I tried connecting my PS3 straight to the modem and was able to achieve NAT 1. But I tried it connecting with the router settings I had before and I'm at NAT 3 again. Again, I know I'm forwarding the right ports and such. I might do those netsh commands you recommended earlier.

But since the modem problem is fixed, I thought I'd try ipconfig again before doing those commands. Again, this is with the modem plugged into the computer.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : [censored]
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-11-11-9E-90-C8
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 68.94.156.1
68.94.157.1

PPP adapter SBC Yahoo 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 76.226.202.32
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 76.226.202.32
DNS Servers . . . . . . . . . . . : 68.94.156.1
68.94.157.1
NetBIOS over Tcpip. . . . . . . . : Disabled

[JohnWill]

The "modem" is a modem/router with a NAT layer as I suspected. You'll never get the secondary router to allow normal connections if it's NAT layer is enabled, since you will never be able to get the port forwarding or uPnP working through two NAT layers.

I'd consider configuring the router as a WAP since it works connected directly to the modem, that will make it transparent to the traffic and still allow you to use the wireless and wired ports on the router.


Connecting two (or more) SOHO broadband routers together.

Note: The "primary" router can be an actual router, a software gateway like Microsoft Internet Connection Sharing, or a server connection that has the capability to supply more than one IP address using DHCP server capability. No changes are made to the primary "router" configuration.

Configure the IP address of the secondary router(s) to be in the same subnet as the primary router, but out of the range of the DHCP server in the primary router. For instance DHCP server addresses 192.168.0.2 through 192.168.0.100, I'd assign the secondary router 192.168.0.254 as it's IP address, 192.168.0.253 for another router, etc.

Note: Do this first, as you will have to reboot the computer to connect to the router again for the remaining changes.

Disable the DHCP server in the secondary router.

Setup the wireless section just the way you would if it was the primary router, channels, encryption, etc.

Connect from the primary router's LAN port to one of the LAN ports on the secondary router. If there is no uplink port and neither of the routers have auto-sensing ports, use a cross-over cable. Leave the WAN port unconnected!

This procedure bypasses the routing function (NAT layer) and configures the router as a switch (or wireless access point for wireless routers).

For reference, here's a link to a Typical example config using a Netgear router

[Kelveeno]

Hey axe,

We have PS3's here at work. We use a netopia 3347 router/modem to connet to the internet. The PS3s are NAT3. However, we map public static IP's (assigned to us by our ISP) to the PS3's (one-to-one NAT) and this allows our PS3's to run at NAT 2. try that and see if it works for you.

At home i use a linksys router and my PS3 is NAT2 without any modifications.

Kelvin