|
WOW Ultra TV - Blocked Ports & Router Access - Please HelpHi all,
I'm having 2 problems. The first one is that I found out WOW is blocking a few UDP and TCP ports I need open. I have a PS4 and a Sony Entertainment Network Account, I am unable to access my account from the url: Https://Account.sonyentertainmentnetwork.com because one of these ports are blocked. This is the Port information I was given by sony customer service:
TCP Ports: 10050,10051, 10040 - 10060 UDP Ports: 50000-60000 - 3478 - 3479.
I was looking at the Arris UltraTV gateway interface and I did not see any way to configure these ports like I would be able to on a normal router. Does anyone have any suggestions on how I can go about this?
My second problem is accessing my personal router settings. Currently my network is set up where I have the UltraTV Gateway as the DHCP server and my personal router connected to it as a wireless access point. But I cannot seem to access the router via 192.168.1.1.
I have already attempted to connect a LAN cable directly from my PC to my router with the gateway disconnected from everything, but It still doesnt work. What am I going wrong? |
|
|
Mine is 192.168.0.1. |
|
|
192.168.0.1 is the ip of the gateway itself for me |
|
|
to mikey32230
OK, first issue... 192.168.0.1 should get you into the Gateway interface (unless you have changed the IP address string). Once you are in, you need to click on the "Firewall" tab. In that section you will find "Virtual Servers" and "Port triggers". Those are the sections where you would unblock the ports you need. Second issue... Personal router settings will be diminished once you set it up as a access point. You can and should still be able to access it, but the 192.168.1.1 address will not be correct. If i am reading your setup correctly, and you have the Arris Gateway as the DHCP server, then you will need to get the router/access point's new IP address from the Gateway. Logging into the Gateway as I described earlier, this time you go to "LAN Setup" and then click on "DHCP". This will take you to a list of all of the devices that are connected to the Gateway and the router/access point. Look for the router/access point's name and that's where you will find the correct IP address. Also, some companies have another way of logging into their routers, a fixed address (e.g. Netgear lets you log into their routers using the address » routerlogin.net as well as the ip address). Check and see if your router's manufacturer has something like this as well. Hope this helps. |
|
NormanSI gave her time to steal my mind away MVM join:2001-02-14 San Jose, CA TP-Link TD-8616 Asus RT-AC66U B1 Netgear FR114P
1 recommendation |
to mikey32230
said by mikey32230:I'm having 2 problems. The first one is that I found out WOW is blocking a few UDP and TCP ports I need open. Unlikely that WOW is blocking any of the ports you have listed. If they were, you would be unable to "open" them by port forwarding. With a NAT ("Network Address Translation") device, unsolicited inbound packets are discarded; unless the device is specifically told where to send them. This is what, "port forwarding" does. Ports are actually "opened" by a running service on the device which is the "target" of port forwarding. I concur with RemyL75 on the AP access issue. Because your personal router is operating as an AP, its IP addresses is assigned by the DHCP server. Also, as an AP, it will not perform any NAT function, so configuring port forwarding on the AP will not be useful; if it can be done at all. NAT function is provided by the WOW-issue gateway, so port forwarding will have to be done on that device. Personally, I prefer using a bridged modem with my own router over an ISP-issue gateway. All ISP-issue gateways can be managed by the ISP from the WAN (Internet facing port); so all of your LAN devices are accessible to remote access from the Internet. This is equally true for DOCSIS (WOW) as for DSL (my ISP, Sonic.net, wants me to lease their ADSL2+ gateway). |
|
ody join:2015-01-24 Naperville, IL |
to mikey32230
said by mikey32230:I have already attempted to connect a LAN cable directly from my PC to my router with the gateway disconnected from everything, but It still doesnt work. What am I going wrong? if u disconnect your personal rounter (PR) from the network entirely then plug in one cable from PC to PR, you should have no problem accessing the router setup pages. problem is you may have forgotten what the IP is. You may want to hard RESET the router, which normally sets it to 192.168.0.1 or 192.168.1.1 (google ur PR on net). Once in you can config it and remember NOT to use 192.168.0.1 because that is the WOW gateway default ip. Once setup, plug the router back into the network, it should get an IP from the Gateway and allow you to use it (wirelessly?). Once on the network, you wont have access to the config pages at 192.168.1.1 (if thats what your chose), you will have to pull it off the network again, plug directly from PC, config it and repeat... |
|
|
to NormanS
said by NormanS:said by mikey32230:I'm having 2 problems. The first one is that I found out WOW is blocking a few UDP and TCP ports I need open. Unlikely that WOW is blocking any of the ports you have listed. If they were, you would be unable to "open" them by port forwarding. With a NAT ("Network Address Translation") device, unsolicited inbound packets are discarded; unless the device is specifically told where to send them. This is what, "port forwarding" does. Ports are actually "opened" by a running service on the device which is the "target" of port forwarding. I concur with RemyL75 on the AP access issue. Because your personal router is operating as an AP, its IP addresses is assigned by the DHCP server. Also, as an AP, it will not perform any NAT function, so configuring port forwarding on the AP will not be useful; if it can be done at all. NAT function is provided by the WOW-issue gateway, so port forwarding will have to be done on that device. Personally, I prefer using a bridged modem with my own router over an ISP-issue gateway. All ISP-issue gateways can be managed by the ISP from the WAN (Internet facing port); so all of your LAN devices are accessible to remote access from the Internet. This is equally true for DOCSIS (WOW) as for DSL (my ISP, Sonic.net, wants me to lease their ADSL2+ gateway). It is the WOW Gateway firewall that is blocking the ports. When turning the firewall off Everything works normally. You mention using your own modem. If I did that, wouldn't I have to give up all the wow ultra TV features like dvr? Wouldn't I need to get other boxes from them for hd channels for each TV? |
|
NormanSI gave her time to steal my mind away MVM join:2001-02-14 San Jose, CA TP-Link TD-8616 Asus RT-AC66U B1 Netgear FR114P
|
said by mikey32230:It is the WOW Gateway firewall that is blocking the ports. When turning the firewall off Everything works normally. That is not the same as saying, "WOW is blocking ports". You mention using your own modem. If I did that, wouldn't I have to give up all the wow ultra TV features like dvr? Wouldn't I need to get other boxes from them for hd channels for each TV? As a "cord never", I don't worry, or think about such things. For me, Internet and television are separate items. I would find the Ultra system too restrictive, if it actually works as you describe. In fact, the reason I don't have a pay TV service is precisely because the service provider is in control of my gear. That said, if you are willing to cede control to WOW, you have to learn the unique foibles, and rules they use to control your access. From your description, you can't use your personal router as a router, as I understand setting up a home LAN. Assuming your WOW gateway has IP address 192.168.0.1, setting up your personal router as an AP means it will just be another TCP/IP device in the gateway DHCP pool. It will have IP address 192.168.0.x; you will need to check the gateway GUI to see what the value of, "x" will be. Port forwarding will have to be done in the WOW gateway, not in your personal router. |
|
Ooma Telo
|
to mikey32230
If you have a firewall on your router, modern routers do, use that instead. Just turn the firewall off on the gateway and use your router's firewall, since every device you have "sits" behind the router.
The gateway is nothing more than a glorified cable modem that brings the internet in to your home. |
|
|
|
I'll definitely do that thank you |
|
Bill_MIBill In Michigan MVM join:2001-01-03 Royal Oak, MI TP-Link Archer C7 Linksys WRT54GS Linksys WRT54G v4
1 edit |
to devolved
Hi devolved. Are you assuming firewall=NAT and turning off "firewall" puts the modem in bridge mode? I don't think that's the case. WOW has some equipment *stuck* in NAT-only and I was lucky enough to get some info from the right person: » Re: Upgrades in the Troy, MI plant? where Just_Dan confirms the Ultra gateway is *not* bridgeable. EDIT: Actually, I'm not sure the Sony ports are INbound like some assumed. Perhaps someone knows the Sony web page involved - are those OUTbound ports? Does the gateway "firewall" block unusual ports OUTbound? I always wince when I hear the generic "opening ports" without a direction mentioned. |
|
|
The gateway will only do NAT, not bridged. But it shouldn't be blocking outbound connections by default. Also, if you put another router behind it using the WAN port so it also acts as a router, the media play won't see DLNA servers behind the other router. |
|
Bill_MIBill In Michigan MVM join:2001-01-03 Royal Oak, MI |
Thanks, lesmikesell, So they are outbound. I knew it was unusual for a web page to require inbound connections and I was editing as you replied. |
|
|
It is not at all clear what the 'enable/disable firewall setting actually does. Most things that need inbound connections will set it up themselves via upnp (enabled in the LAN settings, not the firewall tab). Network game play may need that. Or, you can specifically port-forward certain inbound ports to a device, or use the DMZ setting to send all inbound connections to one inside IP address. |
|