RT-AC87U blocked port(s) ?

[Tom_Hall]

Hi - I've got an odd problem - I'm on VirginMedia Cable, I have VM's SuperHub2, an ASUS RT-AC87U, and a T-Mobile/EE Signal-Box (a mini femto-cell)

I was running with the Superhub (in modem-mode) > RT-AC87U > (wired) Signal-Box and all was working fine (I bought the RT-AC87U back in May),
- until last week when the Signal-Box stopped talking back to T-Mobile/EE, and I lost the ability to take/make calls via the Signal-Box.

I tried everything, rebooting all devices, different cables, went from Merlin firmware back to Stock etc, and even disabled the RT-AC87U's firewall (for a whole night - although I had all my computers powered off)

After a week of getting nowhere with T-Mobile/EE support, I took the VirginMedia SuperHub2 out of modem-mode, disconnected the RT-AC87U, and plugged the Signal-Box straight into the SuperHub2 - and the Signal-Box almost immediately "connected" back to T-Mobile/EE, and I can now make mobile calls via it.

So, I'm wondering if its possible that the RT-AC87U was blocking any ports ?
If I put things back to how they were, is there anyway for me to see (on the router), if anything is blocked ?
Any other ideas ?

 

[red_pope]

Well my friend, I hope this helps you. Remember to do your 100 percent of work. Do your own research always.

https://serverfault.com/questions/26564/how-to-check-if-a-port-is-blocked-on-a-windows-machine
Since you are on the Windows machine, these things can be done,

• Execute the following command and look for a ":3306" listener (you did not mention UDP/TCP). This will confirm there is something running on the port.
  netstat -a -n
• After this, if you are expecting incoming connections on this port and feel that the firewall may be blocking them, you could start windows firewall logging and check the logs for dropped connections
  • Go to the Windows Firewall, Advanced settings
  • Click on the Settings button next to "Local Area Connection"
  • Select "Log dropped packets"
  • Look at the log file location (if not present define one)
  • Click OK
  • Now, when the connection attempt is made (assuming you know when this is done), look at the log file for a drop on port 3306.
  • If this is seen, you will want to add an exception for this port.
• There is one more command to check the firewall state
  (Update for Windows 7 users -- as referred by Nick below -- use netsh advfirewall firewall)
  netsh firewall show state
  • this will list the blocked ports as well as active listening ports with application associations
• This command will dump the Windows firewall configuration detail
  netsh firewall show config

If you have an active block (incoming connections are being dropped by firewall) after you start logging, you should see that in the log.
If you are running an application/service that is listening on 3306, the firewall config should show it to be Enabled. If this is not seen, you have probably missed adding an exception with the firewall to allow this app/service.
Finally, port 3306 is typically used for MySQL. So, I presume you are running MySQL server on this windows machine. You should therefore see a listener for 3306 accepting incoming connections. If you do not see that, you need to work with your application (MySQL) to get that started first.

 

[Tom_Hall]

Well my friend, I hope this helps you. Remember to do your 100 percent of work. Do your own research always.

https://serverfault.com/questions/26564/how-to-check-if-a-port-is-blocked-on-a-windows-machine
Since you are on the Windows machine, these things can be done,

• Execute the following command and look for a ":3306" listener (you did not mention UDP/TCP). This will confirm there is something running on the port.
  netstat -a -n
• After this, if you are expecting incoming connections on this port and feel that the firewall may be blocking them, you could start windows firewall logging and check the logs for dropped connections
  • Go to the Windows Firewall, Advanced settings
  • Click on the Settings button next to "Local Area Connection"
  • Select "Log dropped packets"
  • Look at the log file location (if not present define one)
  • Click OK
  • Now, when the connection attempt is made (assuming you know when this is done), look at the log file for a drop on port 3306.
  • If this is seen, you will want to add an exception for this port.
• There is one more command to check the firewall state
  (Update for Windows 7 users -- as referred by Nick below -- use netsh advfirewall firewall)
  netsh firewall show state
  • this will list the blocked ports as well as active listening ports with application associations
• This command will dump the Windows firewall configuration detail
  netsh firewall show config

If you have an active block (incoming connections are being dropped by firewall) after you start logging, you should see that in the log.
If you are running an application/service that is listening on 3306, the firewall config should show it to be Enabled. If this is not seen, you have probably missed adding an exception with the firewall to allow this app/service.
Finally, port 3306 is typically used for MySQL. So, I presume you are running MySQL server on this windows machine. You should therefore see a listener for 3306 accepting incoming connections. If you do not see that, you need to work with your application (MySQL) to get that started first.

Thanks for the advice - I did research this, and also my post was quite specific


At no time, did I mention Windows (or any other OS) - the Signal-Box should simply

Sent from my GT-I9505 using Tapatalk

 

[Tom_Hall]

(cut off in mid reply) the signal box once plugged in to the network, should just "work" - no need for pcs

Sent from my GT-I9505 using Tapatalk

 

[L&LD]

Tom Hall, hope you are not driving?

 

[Tom_Hall]

No - I'm in the pub, but its raining heavily and the 3g around here is going up & down

Sent from my GT-I9505 using Tapatalk

 

[L&LD]

Points for not driving and for being in a pub.

 

[red_pope]

Points for not driving and for being in a pub.

Once in a while, I do indulge with my spouse in one of the many local pubs in my town. Of course my son will drive for hes {folks}.

 

[red_pope]

No - I'm in the pub, but its raining heavily and the 3g around here is going up & down

Sent from my GT-I9505 using Tapatalk

Could you ping it? Could you access the GUI and verify the ports available? Does it has a manual or is there more information about it in the net? Sometimes is not that hard as it sounds.

 

[Tom_Hall]

The bottom-line is ...

It (the signal-Box), (currently) works Ok with(out) the RT-AC878U - i.e if I have the SuperHub2 in Router-mode
It (the signal-Box), (currently) does not work, if I have the SuperHub2 in Modem-mode, and have the RT-AC878U hanging-off the SuperHub2

- that's why I also asked, if I was to re-introduce the RT-AC878U into my network, if there was anyway I could interrogate "on the router"
eg. via some cryptic ssh/*nix style command), and see if there is any "default" blocking" - even if the GUI shows the it's firewall is "not enabled"

The "other" way of looking at it, is/are there any known compatibility issue(s) with the Signal-Box, and the RT-AC87U ?

I have a list of required ports (supplied from from T-Mobile/EE)
TCP 87
UDP 123
UDP 53
TCP 8080/80
TCP 443
UDP 500
UDP 4500

When I check the Active connections (via the RT-AC87U's GUI), I only ever see the Signal-Box connected to ports 123, and 4500
Unfortunately, Virgin Media's SuperHub2 GUI is so locked-down, that I can't do even simple checks like this

I hope this helps ?

 

[Tom_Hall]

Could you ping it? Could you access the GUI and verify the ports available? Does it has a manual or is there more information about it in the net? Sometimes is not that hard as it sounds.

Could you ping it? -I can "see" from the router that it has been allocated a DHCP address - and YES - I can ping it's ip address

Could you access the GUI and verify the ports available? - the device has no GUI (or user-command interface)

Does it has a manual or is there more information about it in the net? - Looks like EE have taken-down the manual, but it was just a "glossy brochure - no technical stuff"
http://ee.co.uk/help/mobile-and-hom...nd-improving-your-network-coverage/signal-box

Here is a copy of the manual I found on from Nokia's web site:
http://networks.nokia.com/system/files/document/nsn_fapr-hsp_5000_um.pdf

I hope this helps ?

 

[red_pope]

I read the manual (PDF) from Nokia's web site you provided.
Hopefully, you have the same model listed from the Nokia's PDF, it should work.
It does not says anything about compatibility issues with network devices, I'm assuming it is plug and play network compatible.

I read the FAQ from the PDF.

I have an Idea for you to continue testing.


Have you tried to connect it through a non-manageable switch?
This will Bypass, by not using any of the LAN ports from the Asus router.

1-Inter Connect all your devices to the Gigabyte Switch instead. It could be a 12 port switch or 24 port switch.

2- Connect your Asus router to any port of the Gigabyte switch LAN port.

3- Connect your box to any port of the Gigabyte switch LAN port.

That way you bypass connecting, anything to the Asus Router, once you are done, Your ISP issue router will do the the routing.

Check for connectivity and browsing.

If this not work, then you could try to do Port forwarding for the device.

Hope this works.

 

[Tom_Hall]

I read the manual (PDF) from Nokia's web site you provided.
Hopefully, you have the same model listed from the Nokia's PDF, it should work.
It does not says anything about compatibility issues with network devices, I'm assuming it is plug and play network compatible.

I read the FAQ from the PDF.
I have an Idea for you to continue testing.
Have you tried to connect it through a non-manageable switch?
This will Bypass, by not using any of the LAN ports from the Asus router.

1-Inter Connect all your devices to the Gigabyte Switch instead. It could be a 12 port switch or 24 port switch.
2- Connect your Asus router to any port of the Gigabyte switch LAN port.
3- Connect your box to any port of the Gigabyte switch LAN port.

That way you bypass connecting, anything to the Asus Router, once you are done, Your ISP issue router will do the the routing.
Check for connectivity and browsing.
If this not work, then you could try to do Port forwarding for the device.

Hope this works.

If I'm reading your suggestion correct, I've...
Put my ISP's SuperHub2 into modem-mode,
Connected the SH2 to a Netgrear GS108 unmanaged Gigabyte Switch,
Connected a pc to the switch - I can browse ok, but I have an 81.98.x.x IP address (not a 192.168.x.x)
Connected the Signal Box to the switch - but it's status light is just "flashing-red" ie. worse than "flashing green" - so I guess the Signal Box is expecting to be behind a router

Also, I have tried port-forwarding the ports support gave me (no good), and
I've also tried putting the ip address of the signal Box into the Asus Router's DMZ (no good), and
I've tried running with the Asus Router's firewall turned off (no good)

Also, I resurrected my old Netgear wndr4500, but couldn't get the Signal Box to connect through that either (I'm pretty sure that it used to work, and without port forwarding too)

I've currently reverted back to using the SH2 in Router mode - without the Asus router

 

[Tom_Hall]

One thing (so obvious I hadn't noticed it) ...
When I change my SuperHub2 from Router-mode to modem-mode -
My WAN (External) IP address changes (again, so obvious I hadn't noticed it),
So I wonder if the EE servers are getting confused by the IP address change ?

 

[red_pope]

Tom Hall

I don't understand, why you have to change your ISP settings router? Leave everything as a DHCP on your ISP router. I'm throwing the towel on this one. later dude...

 

[Tom_Hall]

Ok - I understand where you're coming from

There are several reasons why I (and several others), use our own Routers ...
The SuperHub2 does not have VPN, Custom DNS'ses, DynamicDNS, Logging is "basic", and it's Wireless is c***
also the gui is riddled with oddities like not being able to use dhcp to set/reserve addresses outside the dhcp pool

Also, one last bit of info - it appears that VirginMedia have recently rolled-out a firmware upgrade to their SuperHub2's which has caused grief for several of their users who use modem-mode and their own routers (like me)
http://community.virginmedia.com/t5...o-v2-01-03-broke-modem-only-mode/td-p/2860733