Port Forwarding Protocol Doesn't Save W330N Gaming Router

When trying to forward ports on the Single Port Forwarding setup page I cannot change the protocol to anything besides TCP. I can select "both" or "UDP" but after I click save and the page reloads the setting is reverted back to TCP. Is there something that stops this setting from working? Is there a way around this problem? When using the Range setup I change the protocol and save the setting, but then I can only forward a limited number of ports. Is there a bug in the software?

Hi.
Yeah,may be it's a bug,but upgrade the firmware and reset the router and configurate it again.It should b work
Good Luck!!!
Thanks
Kind Regards
ing.George Gochev
DSL and Telecommunications Engineer

Similar Messages

Port-forwarding or UPnP on VERIZON FIOS modem/router

I'm trying to help someone access his home network remotely from another location. he just got the new Verizon FIOS network.
i'm new to the world of port-forwarding and UPnP forwarding, but have learned a lot in a short period of time.
I can easily setup port-forwarding and UPnP forwarding (necessary to setup the afp file sharing, screen sharing, etc) on Linksys routers that have those capabilities.
My friend just got the new Verizon FIOS network installed. It is smoking fast both up and down. We figured out that the box Verizon provided him (it's a fairly huge thing) is an internet modem, a router, and a wireless router all in one.
And once we accessed its control panel, I definitely saw places where we could configure port-forwarding........
but it's not quite as straightforward as it is on a Linksys router in that, on a Linksys, if I want to open a specific port, like 5900, for screen sharing, I can easily type in the numbers 5900 and type the IP address of the computer on my LAN that I wish to forward port 5900 traffic to.......or I can do this with UPnP forwarding....either way it is simply and fully controllable.
But on this Verizon box, it seems to have most standard ports and protocols stored in presets that you must choose from. For example, if I wanted to setup port forwarding for FTP traffic, I would choose FTP from the dropdown menu and then the router would automatically know to forward port 21 to the computer of my choice.
but we specifically want to turn on AFP for apple file sharing, which is port 548. On the Linksys, i could simply type port 548. But this Verizon router does not show a service called AFP. It has a nice LONG menu of many different pre-set options, but AFP is not one of them. Would it be called something else on a device like this that is obviously not specifically designed to know Apple's file sharing protocol?
So would anyone know what kind of service I should look for that opens port 548 for file sharing?
Anyone have experience with these new Verizon routers/modems yet? I'd really love to find a way to type everything in manually, but I dunno if that's possible on this unit.
i know there's a lot here. thank you to anyone who knows about this and can shed some light

That doesn't work because applications that initiate outbound connections are given randomly assigned 5-digit port numbers (e.g., 49144) through which the CLIENT communicates. The "well known" port numbers like 548 for afp, 22 for ssh, 80 for web servers, etc., are for the SERVER function to which the server daemon listens. Example: you don't send the request to download your email from your pop 110 (or 995 when using SSL), or from your imap 143 (or 993 when using SSL); that's the port number at the DESTINATION server to where your traffic is delivered, i.e., the port to which that SERVER is listening for incoming traffic. Same for when you send mail, you send from some randomly assigned five-digit port number TO the smtp server's port 25. You can see this by launching Terminal.app from an admin-privileged account and typing sudo tcpdump -i en1 (use en1 for airport, en0 for wired ethernet) and looking at the packet transmissions' headers.

Port forwarding: Base station as bridge or modem/router as bridge?

I use a modem/router (Netopia Cayman 3346) to connect to the internet. It's hooked up to my airport extreme (old round model) to go wireless.
I now would like to forward some ports. I understand you have to set either the airport station or the modem/router as a bridge and then forward the ports on the other device. Am I right so far?
My question: What is the difference (if any) to bridge either one of the devices? Any pros or cons in using Airport as port forwarding device or my netopia? Which one shall I set to bridge mode? Both allow to set port forwarding.
Thanks for clearing this up for me.
Gordon.

I'd like to forward some specific ports. For example port 36391 (TCP/UDP). I know that to do this I have to set one of the two devices as a bridge, and then configure the other device to forward the ports I want. I also know that I can either set up my base station as the bridge or my modem/router.
My question is: which one of the two shall I choose to use as bridge? Airport base station or modem/router? Does it matter or not which one I choose?
Thanks

Port Forwarding and Printing with Static IP Address

Hey there -
I am trying to setup a network printer that can be printed to from anywhere in the world. My organization has 5 static IP addresses given to us by our ISP. Four of those I have on computers, and one of them I have on my Linksys router (WRT54G v.8).
What I want to do is be able to setup a printer on my router that I can print to from anywhere I have an internet connection. My wireless router's static IP address is 74.172.54.XXX - The address on my network is 192.168.7.1 - I have a printer statically assigned the IP address 192.168.7.2 - and I have a port forwarding for port 70 to forward to 192.168.7.2
In theory, I would think that now I could print to 74.172.54.XXX:70 and have no problems. But that doesn't seem to be working. Even printing to 192.168.7.1:70 doesn't seem to work either.
Also, the printer has a web GUI interface that if I type http://192.168.7.1/ into my browser it comes up, so in theory I would think typing http://74.172.54.XXX:70 into my browser it should come up (but it doesn't nor does http://192.168.7.1:70).
Anybody got any suggestions? I tried to do a search about this, but ever Port Forwarding question seemed to deal with gaming (which I have no desire to do). Thanks!
I will include two screen snapshots of what I am talking about:
Thanks for any help.

Is the router setup to accept static connections?
I have my router set up to accept both, so from 192.168.1.100 to 192.168.1.192 the addresses are static the other addresses are given by DHCP.
If you do not define a range and the address your laptop has as static IP conflicts with the address given by DHCP your loose ... as in you get no address.
Set up of that feature may depend on your type of router but usually any decent router will have that capability ... read your manual for specifics about your unit.
Best of luck.
R.
Last edited by ralvez (2009-12-10 00:08:50)

Port Forwarding with Airport Express 802.11n Utility version 6.1

Hi all,
Quick question, hoping it can be solved with a quick answer
Not sure what I'm doing wrong: I'd like to set up port forwarding for Skype and Transmission, however in the airport utility even when I assign the public/private ports to the ones specified in the respective programs (with the IP address for the machine I am using), if I go into Transmission or onto a port checker website the connections are shown as closed for the ports I have selected (on the public side).
I've made a DHCP reservation for this machine to tie it to a given IP address, and I've enabled NAT port forwarding protocol in the Network options (no default host so far).
Also, in case it makes a big difference, right now I'm connecting to the internet via a Cisco DCP3825 cable modem running in bridge mode, with the AEBS in DHCP and NAT router modes.
Any tips?
Thanks!

Sadly I never got it to work. I called up Apple and they claimed that all the ports are open for the Airport Express, but if I run port scanner in Network Utilities none of the ports I specify show up as open unless I select one of the "Default" port categories like "Windows File Sharing". I told this to the person I spoke to on the phone, and they replied several times in a row that they are not allowed to help set up port forwarding, that they can only provide info on how to open the ports, and that even if the ports are subsequently not opened or forwarded they can't provide any assistance. It wasn't a very good conversation. Unfortunately, based on some of the other disucssions I've looked at in this forum, it doesn't seem possible to do conventional custom port forwarding using this version of the Airport Utility. Hopefully someone will correct me though. Sorry I can't be more help.

Port forwarding

wondering if anyone could walk me through port forwarding on a westell e90 610015-06 router. I am trying to set up TCP and UDP for a P2P program(e-mule). After several attempts i can't seem to set it up. Thanks!

Here is what I have set up
Services:
1. imapssl_993t_in all 993
2. imapssl_993t_out 993 all
Exceptions
1. imapssl_993t_in Public Any Public PUBLIC_IP_OF_BM_SERVER (I only want it coming in on this address)
2. imapssl_993t_out Public PUBLIC_IP_OF_BM_SERVER Public Any
Proxy - Generic TCP
original (internal_ip_of_imap_server) port:993 Proxy address: PUBLIC_IP_OF_BM_SERVER port:993
Access rule
Very generic, just allow original port with value of 993.
>>> akeaveney<[email protected]> 1/9/2013 11:46 AM >>>
JackCunha;2122118 Wrote:
> BM 3.8, fully patched; NW 6.5.8. An internet backup service says I need
> to forward external port 443 to the internal backup server's port 4282.
> I have a stateful filter exception for port 443 on my BM server, with
> the destination being the public address of the BM public NIC. Can i
> accomplish what want to do. If so, how?
I am trying to setup this at the moment, yet for IMAP access from
outside to internally. I don't want to hijack the thread, yet someone
might be able to help us both.
I have setup the generic tcp proxy under the BM Server in Imanager and
setup the private address and public proxy address with the port numbers
I want. I also allowed a filter exception from all interfaces to public
and allow the destination as the BM public address, but this still won't
work for me,
Is there something I am missing? I have tried it with the filters down,
but it doesn't seem to be doing the mapping.
Many thanks,
Anthony
akeaveney
akeaveney's Profile: http://forums.novell.com/member.php?userid=6365
View this thread: http://forums.novell.com/showthread.php?t=442041

Router Port Forwarding not working since Mavericks

I have an iMac sat behind a BT Home Hub 3 (an ADSL router, if you're not aware), with several ports (POP3, SSH, HTTP, etc) from the outside world forwarded via the hub to my Mac. Since installing Mavericks (from Snow Leopard), NONE of these ports are now open.
They're open on the Mac, and another machine on my home network can use them locally, but from outside the network, they're hidden. Shields Up shows them as Stealth.
Things I've tried:
Rebooting everything.
Setting the Home Hub up again, forwarding all the ports again.
Turning all the sharing off in Mavericks and then back on.
Trying the same services on different ports.
Trying different services.
Turning off the Mac firewall.
Turning off the router firewall.
Trying the Mac on another IP address and reforwarding everything to the new one.
Putting the Mac in the DMZ.
I can forward ports to other devices on my network (e.g. my NAS) and they work fine, so port forwarding isn't completely broken on the router
Here's the thing though...
On a completely separate network, on a separate Mac (a 2012 MacBook Pro) that went from Mountain Lion to Mavericks, also behind a BT Home Hub 3, EXACTLY the same thing is happening. No ports can be forwarded to the MacBook Pro, but all the ports are open to the local network.
Any ideas? I'm pretty sure this must be a bug in Mavericks as I can't see anything else it can be.

It's not just single port forwarding that has bugs, the entire router has bugs and simply does not work as advertised. I have found the following bugs/aspects of this router that just does not work correctly: 1. If you have to open ports, and who doesn’t, this router will eventually stop accepting packets from WAN>LAN. You will still have Internet access but no open ports. A reboot will fix this problem. Oh, by the way, this router has no scheduled reboot option! <--That would be a workaround but a welcome one for this router. 2. Firewall Access rules do not work!! Yep, a Cisco router and basic functionality simply does not work. I called Cisco and even though the tech saw the router not working denied it was a bug! Said we have to do port mirroring, setup a workstation with WireShark and capture packets so we can debug the issues. That would take several hours. I told him I would have appreciated if Cisco would have debugged the issues with their router BEFORE they shipped the units. Stay away from Cisco Small Business Routers. I wish I had. And if there are any Cisco die-hards out there willing to prove me wrong, just reply to this and please, prove me wrong that the RV series and specifically the RV215W is not JUNK.

Port Forwarding With Shorewall

I have Shorewall setup on my router, but even though I've read on how to set up port forwarding it doesn't seem to work.
Here's my /etc/shorewall/rules.conf
# Shorewall version 4.0 - Sample Rules File for two-interface configuration.
# Copyright (C) 2006,2007 by the Shorewall Team
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2.1 of the License, or (at your option) any later version.
# See the file README.txt for further details.
# For information about entries in this file, type "man shorewall-rules"
#ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL RATE USER/ MARK CONNLIMIT TIME HEADERS SWITCH HELPER
# PORT PORT(S) DEST LIMIT GROUP
#SECTION ALL
#SECTION ESTABLISHED
#SECTION RELATED
#SECTION INVALID
#SECTION UNTRACKED
SECTION NEW
# Don't allow connection pickup from the net
Invalid(DROP) net all tcp
# Accept DNS connections from the firewall to the network
DNS(ACCEPT) $FW net
# Accept SSH connections from the local network for administration
SSH(ACCEPT) loc $FW
SSH(ACCEPT) net $FW TCP 3000
# Allow Ping from the local network
Ping(ACCEPT) loc $FW
# Drop Ping from the "bad" net zone.. and prevent your log from being flooded..
Ping(DROP) net $FW
ACCEPT $FW loc icmp
ACCEPT $FW net icmp
# Accept DNS connections from the local network to the firewall
DNS(ACCEPT) loc $FW
# Allow Webmin access from local net
ACCEPT loc $FW tcp 80
# Allow Transmission Traffic
DNAT net loc:192.168.1.100:51413 tcp 51413
DNAT net loc:192.168.1.100:32000 tcp 32000
DNAT net loc:192.168.1.114:6881 tcp 6881
DNAT net loc:192.168.1.114:8881 udp 8881
DNAT net loc:192.168.1.1:80 tcp 1017
Here's my /etc/shorewall/policy in case it's needed
# Shorewall version 4.0 - Sample Policy File for two-interface configuration.
# Copyright (C) 2006 by the Shorewall Team
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2.1 of the License, or (at your option) any later version.
# See the file README.txt for further details.
# For information about entries in this file, type "man shorewall-policy"
#SOURCE DEST POLICY LOG LEVEL LIMIT:BURST
$FW net ACCEPT info
loc net ACCEPT info
net all REJECT info
# THE FOLLOWING POLICY MUST BE LAST
all all REJECT info
SSH works internally, but not externally, and ping works both inside and outside of the network, web browsing also works fine. I just can't seem to get to anything inside the network from outside of the network. What am I doing wrong?
Last edited by brando56894 (2014-04-02 04:04:34)

Even if the forum policy is more to give people the possibility to help themself, I'd like to post a (hopfully) working configuration for the case above, so everyone trying to use shorewall get an idea how it works.
If someone finds errors please let me know, so I can correct this post. Thanks.
/etc/shorewall/interfaces
# change interface to your external iface
net eth0 dhcp,tcpflags,nosmurfs,routefilter,logmartians,sourceroute=0
# change interface to your internal iface
# if running a dhcp server on your internal interface add ",dhcp" to the following line
# if the interface is a bridge add ",bridge" to the following line
loc eth1 nets=(192.168.1.0/24),tcpflags,nosmurfs,routefilter,logmartians
/etc/shorewall/zones
fw firewall
net ipv4
loc ipv4
/etc/shorewall/masq
# change interface to your internal iface
eth1 192.168.1.0/24
/etc/shorewall/policy
$FW all ACCEPT # FW may talk to everyone
loc net ACCEPT # LAN may talk to the internet
net all DROP info # Drop everything not in rules file
# THE FOLLOWING POLICY MUST BE LAST
all all REJECT info
/etc/shorewall/rules
SECTION NEW
### FIREWALL INCOMING ###
# MISC
Invalid(DROP) net all tcp # prevent connection pickup
Ping(DROP) net $FW # no ping from outside allowed
# ALL -> FW
ACCEPT all $FW tcp 3031 # SSH from internet and LAN
# LOC -> FW
Ping(ACCEPT) loc $FW # Ping from LAN to FW
DNS(ACCEPT) loc $FW # DNS from LAN to FW
HTTP(ACCEPT) loc $FW # Webmin access from LAN to FW
### FIREWALL OUTGOING ###
# not needed, because everything allowed in policy file
### DNAT RULES ###
# leaved out rules not found in network diagram
# add them using the same scheme
DNAT net loc:192.168.1.100:32400 tcp 32400
DNAT net loc:192.168.1.100:8081 tcp 8081
# the following may not work, as it redirects to the FW itself
DNAT net loc:192.168.1.1:80 tcp 1017
Last edited by Tarqi (2014-04-01 23:40:46)

Port forwarding details

Hello, I want to port forward protocol 8443 to a server behind my Cisco router.
My Cisco router is in turn connected to an ADSL PSTN facing router.
I understand the command to do this would be:
ip nat inside source static tcp {localServerIPAddress} 8443 fastethernet 0/1 8443
My question is; do I still need to define "ip nat insde" to fa0/1 of my Cisco router ?
Do I need to do anything else ? (n.b. I have already opened ip the port on the ADSL router and pointed it towards my Cisco router)
Thanks for confirmation.

You could just point your ADSL NAT directly to your sever as well. That should work if your Cisco router isn't currently NATing and the ADSL router has a route to that subnet.
Also no you don't need the IP NAT source list. The static NAT is all you need.
Sent from Cisco Technical Support iPhone App

Home Hub 3 Port forwarding for Netgear Stora

Hi,
I have had a Negear Stora on my home network with a HH3 for about 6 months. Up untill about 10 days ago, all was good, however now when i try to access it remotely via the mystora.com web portal, i am getting the following error messages
Stora is Online,
but cannot be accessed remotely.
Your Stora is not currently accessible. This may be for several reasons:
• Your ISP is not allowing Internet traffic to your Stora
• A firewall is blocking internet access to your Stora
• Port forwarding is not correctly configured on your router, or UPnP is disabled
I have enabled UPnP and have turned of the firewall off, but still no joy.
Is anybody else having this issue? Can somebody please guide me threw the port forwarding as i dont want to braak anything else.
Thanks in advance
W

There is a guide to port forwarding on this page.
Port forwarding problems
If you need more specific help, then please ask me.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Port Forwarding To Two Macs with Port 22 limitations

This is another port forwarding/port 22 issue and I've look around and not seen an answer to my specific problem. I work for a business that has an in-house ad system that runs on a Mac Mini. I have been accessing that Mac Mini remotely because we set up port forwarding through the Linksys rounter that is at the business using port 22. This is the only port that works for this connection to the mini and the software.
We are now adding a second Mac Mini to send the ads to a different set of monitors. I can't set up port forward to the new mini on the same port so I don't know how to connect to this mini remotely. Is there a way to get into the first mini through port 22 and then somehow communite to the second one through the first? Is there another way to do port forwarding...or have the linksys router switch from one mini to the other when a request comes in? There will only be one remote computer trying to reach either Mac Mini so there will never be simultaneous traffic coming in. Any help would be appreciated!
The linksys router is critical to the business becasue a host of other devices are forwarded though it as well.
Thank you.

klara wrote:
Having set up my IP camera with HH4 successfully, I've now got another one and would like to set it up as well. I gave it a unique, static IP address which my router can see fine. When I try to set up port forwarding, I get a message saying:
"The game or application you’ve selected conflicts with an application (IP Cam 1) you’ve already assigned to another device. Please remove the other application or select the same device."
I am not being given the option to select the same device.
I'm now wondering if port forwarding to two identical devices actually works in principle with HH4? Has anyone else done this?
If in the Home Hub 4 A you go to
Advanced Settings
Firewall
Port Fowarding
Manage Games and Applications
You get the following statement:
"Each game or application can be assigned to only one device on your home network"
I would think that the only way round your problem is to have each Camera running a different application or the same application with a different name.
Does the remote browser app need to know the application name or just the device name ?
If you think about how Port Forwarding needs to function you need a way whereby the remote user needs to be able to tell the Hub what Camera to talk to.

Port Forwarding on Home Hub 5 not working

Hi,
Is anybody else having problems getting ports to forward on their Home Hub or Home Hub 5?
I am a new BT customer, less than a week infact and BT have been utterly hopeless in getting this resolved. All they do is send me instructions for port forwarding on a homehub which I do not need and tell me that i need to pay for their tech support to investigate it further which is freaking ridiculous considering port forwarding is an essential part of any router and this router is brand new, less than a week old. (Do BMW sell you a car and then refuse to take responsibility for a broken engine?)
My other option is buying an ADSL 802.11ac router for £150 which out of principle, i dont think i should have to do. One of the reasons i came to BT in the first place was because the homehub is supposed to be one of the best free provider supplied routers around.
Please only reply to this if you know what you are talking about or have experienced this same issue yourselves. I reiterate that I have not missed any configuration steps on my part and this is a case of the homehub simply not working as it is designed.
Scenario:
I like to have remote desktop access to my home computer from external networks. I do not use 3rd party software such as 'log me in' or 'team viewer', I like to use Microsoft Remote desktop and had been doing so for years with my Sky broadband until last week.
I have dynamic DNS running on my machine which updates my constantly changing external IP to the dns server so dont worry about that, thats all good.
I have correctly set up the forwarding of TCP 3389 to the static I.P of my home desktop on the homehub (and rebooted and or factory reset several times)
Result:
Nothing. The homehub displays as though it has forwarded the ports yet i am still unable to remote in from an external network. The port shows as closed when i run a port scanner.
The same goes for other ports I have tried to open. For example, my Xbox One.
BT are sending me out a replacement Hub to try but I fear that this will have the same result as i have seen a few other people post with the same issues.
If anybody has experienced and or resolved this, please let me know and i will be forever grateful
Thank you

When you do a major network revision always reset the TC to factory and start over.. it simply remembers too much of the last setup.
Plug WAN TC into the HH5 and run through the airport utility again. The TC must go into bridge mode. It then should work fine, but I recommend particularly with Mavericks you use strict naming.
Not apple names.. long, loose and loopy.
Names that are short, 2-10 characters is plenty but make an upper limit of 20.
No spaces..
Pure alphanumeric.. no apostrophe or any other odd character.

Can only port forward port 80, other ports does not open.

I am trying to open three ports on my AE (7.6.1), but the only port that actually opens (if set) is port 80.
- The Airport Extreme is the router and no additional router is in place
- I have given the three cameras (that I want to access from Internet) static IP
- I have trired to open three ports for those (45101, 45102, 45103)
None of above ports open, but if I change one port to 80, that port opens and one camera can work. This is really strange and any suggestions or help is much appreciated!

As you don't want to use the modem as router I would recommend to reconfigure your modem into "bridge" mode. In bridge mode it works like a simple modem. You then have to configure your WRT for your internet connection (usually PPPoE for DSL or DHCP for cable). With this setup, you don't have these chained routers and the WRT has a direct connection into the internet (i.e. the WRT shows your public IP address on the Status page).
Some chained router setups shows problems with drop outs, connection loss and similar. I recommend to use only one router in home setups.
On a sidenote: port forwarding is not related to firewall functions. The reason why you need port forwarding is because a router does "NAT" (Network Address Translation). You use private IP addresses inside your LAN (e.g. 192.168.1.*). Private IP addresses are not routed into the internet. Any internet router will immediately drop packets with a private IP addresses. Thus, your router does NAT to map your private IP address to your single public IP address. It's in the nature of this mapping that unsolicited incoming traffic from the internet is dropped unless you configure port forwarding. That's simply because the router would not know where to sent a packet on a port 1234 received on its public IP address unless you tell it. Thus disabling the firewall on a router won't change a thing.

Add 2nd ix2-dl NAS to router. How to port forward 2nd device?

I would like to add a 2nd ix2-dl to my DSL router. The first ix2-dl works well, but I am already port forwarding 443, 50500-50599 with this 1st router's ip address. Router will not let me forward the same ports to the second ix2's ip address without cancelling out the 1st ix2. How do I fix this? I'm using Windows7 and a DSL Actiontec router 192.168.0.x. Thanks!

This is a model depending router issue:
try the following :
Map eg. 50500-50505 to <Unit1-ip-adress> 443, 50550-50555 to <Unit2-ip-adress> 443 rather than a port range.
Ant then have a try with e.g. https://<dny.dns>:50501 for unit 1, https://<dny.dns>:50551
Various PCs / Laptops ( sorry I still really love Dell and Fujitsu ;-))
Supporting Customers ix2s and ix4s -- Love Networking ( not only technically ).
I am not a Lenovo Employee.
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!

Port Forward: Conflicts with all of them.

A bit about me: I am an IT professional 20+ years so I know how to port forward
Situation:
I had a Actiontec Gen1 router. A technician came out the other day and tried to resolve an upload speed issue. As a result, he replaced the ONT and the Router to a Gen2. He got it all up and running and left. My issue started 20 minutes after he left -- when I sat down to reestablish my port forwards.
When I tryed creating my first port forward, I got a warning message about a conflict. I looked at the list and all I had were 3 preset entries:
--Localhost                               TCP Any -> 4567
--192.168.1.100:63145          Application - TCP Any -> Any
--192.168.1.100:63145          Application - TCP Any -> 1
Now, I have done port forwards a lot with my previous router so I was a bit taken back. I did a factory restore on the router and tried to create another port forward - still conflicts.
I knew something was up so I called Verizon. A tech didn't get anywhere so they put me on the phone with Actiontec. They had me try to create a port forward and got the same results. They said the router was corrupt and to have Verizon send me another.
I got the new router in today. While the tech was setting it up in the basement, I quickly tried to create a port forward on it and it worked. I was excited and waited for him to connected it to the WAN. Once he did his thing and established outside connectivity, I tried to create another port forward, and it failed. I asked him to give me back my original Gen1 router so I could use it to troubleshoot. He did with the rule that I call him when I was done.
I got Verizon back on the line and they couldn't help. They then got me on the phone with Actiontec. A couple hours later, they still had no answer. One thing we found though was that they were also not able to connect remotely. They tried 443 and 8080 - nothing worked. I also found that I was able to create UDP port forwards - they worked fine but as soon as I tried any TCP ports, the always came back with a conflict.
Actiontec said the issue was with Verizon and that I should work with them again, so I called Verizon.
I got a great tech who was really going the extra mile instead of giving me the infamous "We don't support that". He too couldn't access the router remotely and we tried just about anything under the sun. For giggles, we decided to put my old Gen1 router back in place. He wanted to reset it to factory defaults so we did. I took a screen capture of my original port forwards though first. When we restored it, it was also stating that there is a conflict when I created a new port forward.
I took a look at my screen capture of my original Gen1 router (this is the one that was originally working over the last year) and I noticed that its 192.168.1.100 entry was set to go to Application - UDP any -> 63146. After resetting it to factory default, Verizon is now setting it to the two setting I documented above.
So now I am questioning Verizons settings that they are pushing down to the router.
My next step was to disconnect it from the WAN completely, do a factory reset and see if I can create a port forward. After doing that test, I was able to create port forwards - TCP, UDP -- they all entered without a conflict. As soon as I connected the router to the WAN and Verizon pushed their settings, it broke again.
The technician did all he could. It is Sunday today and the higher tier techs do not work on Sundays so he said he will have them contact me tomorrow. I sure hope they can resolve this!
So this is the deal:
-Go into your router and try to create a port forward. Pick anyone from the list that includes a TCP port. If you get a message stating there is a conflict, you are most likely in the same boat as I. I would bet anything that Verzion cannot access your router remotely too.
-If you ARE able to create tcp port forwards, then I would highly suggest that you do not do a factory reset. When doing so, I would bet anything that you will no longer be able to create those forwards.
-if you are able to port forward fine, do me a favor and tell me what your 192.168.1.100 port forwards are that Verizon throws in there. If I were to bet, I would bet that the ones that work are set for Application - UDP any -> 63146; If they don't work, I would bet that they are set to:
--192.168.1.100:63145          Application - TCP Any -> Any
--192.168.1.100:63145          Application - TCP Any -> 1
Anyway, that is my story. I spent a whole weekend with Verizon and I am still not working. Any data from the community will be helpful. I want to know if this is a global issue or if it is only affecting me. I have had this happen with 3 routers, 1 gen1 and 2 gen2's.
Thanks for your help in advance.
Solved!
Go to Solution.

Finally - a solution. *wipes brow*
First off, I want to state that the networking group located in the Syracuse - all the other tech need to visit them for a week and learn:
- How to talk to a customer (what to say and not to say)
- How routers work, how they can be configured, and what they are capable of. Basically, learn a bit about networking.
- Listen to the customer - they may know more than you.
Anyway, thank you very much Syracuse Team!
While working with the tech (this guy was awesome and actually listened to me about the automatic port forwards that were appearing from Verizon), he decided to to use the RJ45 network WAN connection in addition the COAX. My setup was setup to only use the COAX connection - it's been that way for over a year now.
The tech turned set it up so that my data was going through the RJ45 and the TV was going through the COAX. When he did this and we reset the router to factory, the Verizon forwarded ports were no longer showing up and as a result, I was able to create ports at will without conflict.
So beware all of you who are setup to only use the COAX connection. It appears that one of my set top boxes was now throwing in the port forwards that I noted in the original post and those were screwing everything up. Go figure that, eh? I wonder who said that some 14 tech hours ago?
Anyway - if you are unable to create port forwards without a conflict error, call up Verizon and tell them the issue. If they act like they never heard this, tell them about my situation and that adding the RJ45 connection in addition the COAX is the solution. Just make sure you reset your router to factory when they are done or else those odd port forwards won't clear.
Peace out and good luck!

Port Forwarding Protocol Doesn't Save W330N Gaming Router

Similar Messages

Maybe you are looking for