What ports can be opened for the NVG589?
I would be grateful if someone could have tell me what ports AT&T will actually route through an NVG589 to a service in my business so I can re-establish remote access to the computers at our family business as the way I was doing remote access using port 22 was blocked by AT&T recently. I put more details on what I was doing until I was blocked below. I can not find a list of what ports are allowed - could someone point me to this information. If there is a recommended secure remote access method please let me know.
The full details:
For about the last year I was accessing VNC using the ssh port (22) and ssh certificates for security after doing remote access less securely other ways for many years. I access I have done involve using the Gaming/NAT menu to open at least one port. For security I had switched to forwarding my the VNC port (5900) to port 22. This worked fine through the evening of patch Tuesday in May but the next morning (Wednesday) the VNC the connection no longer worked. After restarting all computers and the NVG589 it it still failed. Locally within the business (behind the NVG589), I could connect VNC from one computer to another using the port forwarding showing that everything was OK on the server side. Using traceroute it appeared to me that a certain SBC/AT&T server was blocking the connection though I did not confirm that port 22 was being blocked by this server. Repeated calls to support got no resolution as the support people seem only able to make changes the NVG589 firewall using the gaming/NAT menu which is exactly what I had been doing for years. Finally support agreed to send a technician. The technician was able to call some US-based support center that I don't have access to and was able to find out that port 22 is no longer allowed. This information does not seem to be available by calling support (at least I was not told it in 6 calls). For the past couple of months I have been driving into the business because I am still not able to resolve this issue.