US Telco Support > AT&T > AT&T West > [Modem] Motorola 2210-02 Port Forwarding

[Modem] Motorola 2210-02 Port Forwarding

The modem is in DMZ mode and can't be changed without hacking it. There is no port forwarding to set up.

reply to Nathan
So is there no way for me to really be able to open port 3724?

I'm willing to try any other options... I've forwarded it on the router and with windows firewall.

reply to Nathan
All port traffic passes through our 2210 modems to the ethernet port. Nothing is blocked by the modem (DMZ) at any time whether bridged or in PPP on modem mode. So port 3724 is open all the time.

You might have to have the modem pass the public IP to your router, if the modem isn't bridged, for this to work properly.

If you had s southern-style modem (one issued in the old BellSouth region), you would have a working router operating in the modem AND you would have to port forwards traffic through it. You don't have one of those modems, do you?

Disconnects from games can sometimes be caused by excessive number of session (connections) open at once. This overflows the modem's NAT table. Even though all port traffic is passing through the modem, it still keeps a table of all the connections in its memory as if it was doing NAT. Bridging the modem is the best solution to this problem, but even bridging may not solve it completely.

I bridged the modem the night I got it, I heard that was a better way to set it up. I have the router on PPPoE, and I've port forwarded on it.

Since it's bridged and that may not solve it completely, there isn't much I can do with this modem at this point is there? The advanced tab for the modem has severely limited config options and I can't do a lot with it.

Well, I don't really know a lot of places that check for closed ports... The only one I've ever had someone tell me to use is GRC's ShieldsUP!

Running that on 3724 with the custom port probe it says that the port is closed.

I still get dc'd with this modem but it's incredibly infrequently compared to the old modem I had, which was a 2Wire HomePortal 1000HW. Just trying to get rid of the rest of the disconnects. :P Thanks for the help so far.

When GRC ShieldsUP! reports that a port is "closed", the usual interpretation is that no service is running. If you have a personal firewall running on that computer (or Windows XP/Vista), check the firewall logs. You should see a probe from an IP address between 4.79.142.192, and 4.79.142.207 (those are taken from the GRC-SU site).

You "open" a port by running a service. You can check what ports have services listening by running 'netstat -a' at a command prompt.

Just for grins, here is my GRC ShieldsUP! result:

----------------------------------------------------------------------
 
GRC Port Authority Report created on UTC: 2008-07-27 at 00:06:18
 
Results from scan of ports: 0-1055
 
    2 Ports Open
    0 Ports Closed
 1054 Ports Stealth
---------------------
 1056 Ports Tested
 
NO PORTS were found to be CLOSED.
 
Ports found to be OPEN were: 25, 80
 
Other than what is listed above, all ports are STEALTH.
 
TruStealth: FAILED - NOT all tested ports were STEALTH,
                   - NO unsolicited packets were received,
                   - A PING REPLY (ICMP Echo) WAS RECEIVED.
 
----------------------------------------------------------------------
 

Ah alright. Well, I've done what I could outside of playing with network card settings(which I'm not familiar with so I won't do) and doing port forwarding so I guess I'm about out of luck with this issue. :\

Thanks for the help with it. Wish getting the new modem would have fixed it completely but I guess that's how it goes.

Remote control check on Windows Firewall permissions.

C:\Documents and Settings\Megumi_User>netstat -a
 
Active Connections
 
  Proto  Local Address          Foreign Address        State
  TCP    megumi:24              localhost:0            LISTENING
  TCP    megumi:smtp            localhost:0            LISTENING
  TCP    megumi:1547            localhost:0            LISTENING
  TCP    megumi:1547            kozue.aosake.net:2939  ESTABLISHED
  TCP    megumi:2422            kozue.aosake.net:netbios-ssn  ESTABLISHED
  TCP    megumi:4799            lorri3.hupkid.us:netbios-ssn  ESTABLISHED
 

so are you saying that the modem doesnt block or restrict port access right?

The only way an AT&T (SBC-region) modem will block any inbound traffic is if you set your attached computer NIC or router WAN port to be a static IP in the subnet of 192.168.1.x where x is any octet that is NOT 64.

... or if you get into the modem's CLI and start changing the cfg settings. Accessing the CLI is something most users won't attempt.

reply to HokageOwnage
As long as the device connected to the modem is either getting the public IP address, or 192.168.1.64 from the modem, the modem does not restrict port access.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum