We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Open ports on SpeedStream 5851 DSL Modem

Mach70803
Mach70803 asked
on
Medium Priority
3,725 Views
Last Modified: 2013-12-14
I am having a tough time trying to figure out how to open ports on the SpeedStream 5851 modem.  The modem is quite user unfriendly.  I have dug through the manual and I cannot seem to understand the process.  I downloaded a GUI tool, but it only has the option to turn the firewall on or off.
Comment
Watch Question

Systems Engineer
Top Expert 2005
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
OK, the following lines are now in the diagnostic output:

192.168.0.254 tcp all ports
192.168.0.254 udp all ports

but ShieldsUp! reports that everything is still closed.  I have a 16-port hub connect to the modem and about eight computers hooked up behind it, including my Win2k3 Server.  Any ideas why the ports are still closed?

Author

Commented:
Oh, the firewall has been turned off.
Fatal_ExceptionSystems Engineer
Top Expert 2005

Commented:
So, you basically followed this advice, and opened ALL TCP/UDP ports..??:

1. Launch the command line interface by selecting [Start > Run] and entering [cmd] if you are in Windows 2000 or XP, or [command] if you are running Windows 95, 98, or Me.

2. Enter [Telnet 192.168.254.254] or [Telnet xxx.xxx.xxx.xxx] where "xxx.xxx.xxx.xxx" is your router's IP address if you have changed it from the default setting.

3. You will then prompted to [Login]. Enter [admin] or the appropriate login if you have changed it from the default setting.

Note: Our routers do not use a separate User Name and Password; just a single login, which is [admin] by default.

4. To open a port enter the command [sys addserver <tcp or udp> <port>], then [save].

Example: You want to use Terminal Services on your PC. The PC's IP address is [192.168.254.10], and you need to open TCP port 3389 to use Terminal Services. Your router command would be:

   sys addserver 192.168.254.10 tcp 3389

5. Enter [save] which will save the command into the router's flash memory, which contains all its configuration data.


Fatal_ExceptionSystems Engineer
Top Expert 2005

Commented:
The above is, for lack of better terms, a way to forward ports to a specific IP address..  I assume that you want to be able to access your server for some specific reason, such as an RDP (port 3389) or ftp (port 21)..??  Is this correct, or can you tell me specifically what you are trying to do here..??

Author

Commented:
Yes I followed the directions to the point.  I would like to be able to access all computers behind my network eventually via VNC.  At the moment though, I am using a simple 16-port hub.  I would like to replace it with a router/switch, but I didn't want to do so without making sure the modem could be configured to allow all traffice through to the router/switch.  I think eventually I am going to install a second ethernet card in the server and have it be between the modem and the router/switch.
Fatal_ExceptionSystems Engineer
Top Expert 2005

Commented:
I believe that VNC uses 5800 / 5900 for their ports..  But I am a little concerned that you are not able to open any ports period..   Have you tried to access your Lan from an external point..??  Although ShieldsUp is a good place to test your firewall and routers, it is not 100% reliable..  I would try testing this from outside, just to make sure that these ports are not open or mapped..

Another recommendation..  If you want to use VNC products, I suggest you try TightVNC as it gives you a little more security than the plainJane version...

FE

Author

Commented:
I will try to connect from the WAN side as soon as I get DynDns setup since we don't have a static IP address.  I will look into TightVNC.  BTW, the points are yours.
Fatal_ExceptionSystems Engineer
Top Expert 2005

Commented:
DynDNS is pretty straight forward and easy to setup.. You should have no problem there.  I have used DynDNS.org in the past, but there are quite a few other providers of this service, such as ThatIP..  (which I might suggest is more reliable..)

http://www.thatip.com/

Personally, if I know I am going to need to access my home server during the day from my office, I usually just ck my IP address before I leave, and use it for a RDP (TS) session to remotely get into my LAN...   Sometimes it does not change for months at a time (I have had the current one since last August..)  

Good luck, and thanks for those points..

FE

Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.