|
|
|
|
Joined: Feb 2017
Posts: 23
Member
|
|
Member
Joined: Feb 2017
Posts: 23 |
Update-
Using a non-default port in OSDM, I was able to connect to the remote system and disconnect the foreign IP address that was blocking our remote access.
Since port 5091 is forwarded to the system LAN IP address in the remote site firewall, I used this port as the Data Port instead of 5090.
This has only been used on one site at this point, but I will try again when I run into another site that is blocking remote access and returning a "Using Installation Tool..." pop-up.
If anyone else can verify, please respond.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Apr 2007
Posts: 620 Likes: 2
Member
|
|
Member
Joined: Apr 2007
Posts: 620 Likes: 2 |
Way back, I was told ports 161, 162 TCP should be blocked on the firewall. Can't remember why. Something about unwanted requests maybe?
|
|
|
|
|
Joined: Jan 2005
Posts: 340
Member
|
|
Member
Joined: Jan 2005
Posts: 340 |
I know this is an older post, but I just had this happen to me as well on port 5090. Changed my port to 5091 (which I always open up as well like joshuacook stated). Used port 5091 and it showed me the ip address of who was connected (some ip address in amsterdam). I disconnected them and was able to log back into port 5090. Just wanted to share the information.
|
|
|
|
Forums84
Topics94,543
Posts640,074
Members49,857
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (ffej010),
144
guests, and
37
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
