Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Name: Analyst
Anyone else who does onsite services been having problems with getting alternate port number forwards on Verizon FIOS routers to work? I use an alternate port number for Remote Desktop (lets say 6000), and twice when I had a client switch to FIOS (home and business), the port forward doesn't work. A telnet test doesn't even indicate a connection. But it works internally and worked with the previous routers, even the DSL modem/routers they had. I spent about an hour once with Verizon support, but the guy couldn't figure out why the rules wouldn't work and he eventually went with the party line, "Verizon does not support port forwards, so there's nothing more we can do."
The predefined service ports seem to work ok like SMTP and PC Anywhere, thankfully, but it just seems these custom ports do not. Anyone else run into this?
Assume that I already did an Internet search.
There was similar thread just the other day and the answer was a static IP was needed on the target machine.
0 
I've setup routers and port forwards for years, and yes the target was a statically set.
Assume that I already did an Internet search.
0
I wasn't doubting your experience, I was just mentioning a similar situation. What router is being used now? Is it a Westell by any chance?
0
I've been searching Google and apparently you aren't the only one having a problem with actiontec. There is a lot of talk but no real solution. One suggested test was to put the machine in the DMZ.
0
Well, that was what I did for one of my clients as a workaround: I just cascaded a Linksys router behind the FIOS router and put the WAN port of the Linksys in the FIOS DMZ. The DMZ works, custom ports do not.
So I was wondering if anyone else has run into this problem.
Assume that I already did an Internet search.
0
As luck would have it, Verizon added a service for me today and they gave me an Actiontec M1424WR router. They upgraded the firmware too. I set up port forwarding for SSH on port 22 to my Unix box and it worked. I added the protocol and the IP of the Unix box in the web interface. I also lowered the setting to Minimum Security (Low) in the firewall section. Medium or high rejects all incoming requests. Did you set yours to low?
0
Yeah. Try changing your RDP port number to a customer port number and see if your port forward will work.
Assume that I already did an Internet search.
0
I tried it and it didn't work. I enabled RD on the PC (XP Pro desktop), forwarded the port in the router and added the exception to the firewall. When it didn't work, I disabled the firewall, which didn't help. I connected to my neighbor's wifi, also an Actiontec, with my laptop and lowered his firewall settings.
Nothing worked. I could ping my external IP but when I port scanned it, port 6000 was not opened. So, the Actiontec is not opening the port.
0
Check out this discussion. I think it will answer your questions:
http://forums.verizon.com/vrzn/boar...
It help me. I am building a server at home using FIOS.
0
Actually, we were past that stage already since I was able to port forward SSH connections, which are TCP, to my Unix box. It's Remote Desktop on port 6000 that wasn't opening. The router listed it but when I port scanned it from my neighbor's network, the port wasn't opened. That means that actiontec never opened the port.
0
You can actually make a telnet connection to an RDP port as a test, and to SMTP as well.
Assume that I already did an Internet search.
0
I used to telnet to port 25 all the time when SNTP servers didn't have the expn command disabled.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
