|
|
Joined: Dec 2008
Posts: 83
Member
|
|
Member
Joined: Dec 2008
Posts: 83 |
Hey folks,
New Summit first time set up.
Working on trying to access it remotely through my NetGear router.
On SBX I have had success using the port forwarding as outlined by Vertical. (No problems)
Public I.P. address is accessible as I have my router setup for remote administration and it works fine
The question is what are the proper settings in the Summit, router, and what is the proper connection string in your browser?
I assume you go to PGM 160-161 line 29 (Web Server Port / TLS for Web)
Default= Port set to 80 and disabled.
I would assume I would need to enable that setting, change the port, and turn on port forwarding for that new port on my router.
In the browser https://(router IP):(Port Number)
Unfortunately I tried that with port 5003 and locked myself out on the LAN. Had to reload the Summit to get back in.
Thoughts?
Thanks!
|
|
|
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: Aug 2003
Posts: 5,154 Likes: 5
Moderator-Vertical, Vodavi
|
|
Moderator-Vertical, Vodavi
Joined: Aug 2003
Posts: 5,154 Likes: 5 |
I wouldn't change the port number for the KSU as this could get confusing for the end-users that wish to connect to the KSU through the local LAN.
If you can't use port 80 on the WAN, use another port and have the router NAT it to port 80 on the KSU.
If you didn't enable TLS, then you should use https://routerip:portnumber -not- https://routerip:portnumber
|
|
|
|
|
Joined: Jan 2008
Posts: 3,821
Retired Moderator
|
|
Retired Moderator
Joined: Jan 2008
Posts: 3,821 |
You have to create a unique remote web access user id and password or it will not let you long on...the Summit sees that the access request is coming from a different subnet, it will appear to take the user name and password but you will get a log on failure.
www.myrandomviews "Old phone guys never die, they just get locked in some closet with an old phone system and forgotten about" Retired, taking photographs and hoping to fly one of my many kites.
|
|
|
|
|
Joined: Dec 2008
Posts: 83
Member
|
|
Member
Joined: Dec 2008
Posts: 83 |
Worked like a charm when I added the port forwarding to include port 80.
Also made sure I created a remote access login
Thanks guys!
|
|
|
|
|
Joined: Dec 2008
Posts: 83
Member
|
|
Member
Joined: Dec 2008
Posts: 83 |
Thanks NFC and Derrick,
Remote access is working fine using port forwarding on the router for port 80.
NFC made a great point about screwing up access on the local lan from the end users access/perspective.
So use to being the only admin that needs access to the system.
This forum has been a great learning experience thanks to you guys
|
|
|
|
Forums84
Topics94,470
Posts639,723
Members49,827
| |
Most Online5,661
May 23rd, 2018
|
|
|
3 members (Toner, justbill, C5Z),
411
guests, and
82
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
