Westell A90-9100EM15-10

[old_forum_maikeru-sama]

I just got Verizon Fios installed and I am having a really hard time opening up Port 3389, which is for Remote Desktop. I have looked all over the Internet and portforward.com tutorials but just can't get it to work. My modem is the Westell 9100.

Any help would be greatly appreciated.

[old_forum_maikeru-sama]

First, I have searched the forum to make sure this topic has not been covered.


I am having trouble opening port 3389 for Remote Desktop.  I read the PDF manual that comes with Fios and set everything up as it stated.  After this didn't work, I contacted Verizon and they gave me a link to a few Portforward.com guides.  After the guides didn't work, I started searching on the Internet to see if there were any solutions and that is how I found this site.


To give kind of a overview of where I am at, I currently have the settings noted in this tutorial:
http://portforward.com/english/routers/port_forwarding/Actiontec/MI-424-WR/Echolink.htm


The only exception is that I have given the computer that will be accessed via RDP a static IP address via the Advanced Menu.  Also, I changed the Destination Port from 3389 to Any as suggested by several people.  Last, instead of using the computer name, I use the IP address (192.168.1.2) for the localhost name and IP.



Also, the Port Checker Software at the bottom of that guide says that Port 3389 is locked or in use, which seems odd.



RDP worked with Time Warner and Uverse, so I know my PC is configured correctly.


Any help would be greatly appreciated.



Question:

The Technician told me that the only way you can use Port Forwarding is if you upgraded to a Business Account.  He said I would have to put my PC on the DMZ (something I don't want to do) to use RDP.  Is this true?  I contacted Verizon and they told me the only port that is blocked is 80.

[old_forum_maikeru-sama]

Here are some images of some of my settings:
http://img263.imageshack.us/img263/2017/7282009125006pm.jpg
http://img248.imageshack.us/img248/8705/7282009124931pm.jpg
http://img125.imageshack.us/img125/596/7282009124834pm.jpg

[old_forum_maikeru-sama]

Just spoke with a member of the "premium" support staff and he concluded that my settings are correct.

Not sure what to do at this point.

[old_forum_The_Nephilim]

Hi, What is the make and model of your Router??

There are a few things wrong but lets start with what Router you are using ;)



-Gerald

[old_forum_maikeru-sama]

Hi, What is the make and model of your Router??

There are a few things wrong but lets start with what Router you are using ;)



-Gerald

Gerald, thanks for responding.

The Model is Westell A90-9100EM15-10.

[old_forum_maikeru-sama]

Gerald, I will be checking the forum throughout the day.  I am interested in your comments regarding something being wrong.

Thanks

[old_forum_maikeru-sama]

Just fooling around with the settings, I changed "Network Address" to be "Any".  Sucks, because I will be billed for the Premium Tech Support which was worthless.



In the image below, the "Network Address" value should be "Any".

Also, after Verizon Fios was installed, my computer would freeze for a split second everytime I would open up anything (apps, folders, browsers etc etc).  Eventually, I looked in add/remove program and the technician had installed 1 program that was 80MBs and another that was 40MBs and after removing these applications, my PC started running like it did before Fios.

[old_forum_The_Nephilim]

Hi Is the westell the only device on your Network besides the PC's??

If so then we need to find out what the Routers DHCP Start & End IP's are. so log into the Router goto Status look in there for DHCP there should be a Start & End IP in there.. what is the Start & End IP??

[old_forum_tedtrp]

I may of detected a cross posting (same issue by the same user on more than one site), and this issue may be already resolved?

The cross posting that was detected: Verizon Community Forums -> Residential Products and Services -> FiOS Internet -> A question and help with Westell 9100 and Remote Desktop

Short summary, without me re-posting what was said over there.

It is because the port checker that portforward.com has a built in server in it, it was trying to listen to the same port that Remote Desktop was listening to, and you can never have two servers on the same computer listening on the same port.

This can be proven with a tool called CurrPorts fromhttp://www.nirsoft.net which tells what is listening on what port (and with trial and error). ;)

^^