Page 1 of 1

See message via browser in local

Posted: Fri Mar 17, 2017 9:59 am
by saitok
Hello everyone,

I want to see Switch message via Internet Explorer, but I can't.
My Switch 13.1 is installed into Windows Server 2012 R2, and the browser is in the same machine.
When I try to connect to, I just get the alert below.
- - -
This page can’t be displayed
Make sure the web address http://127.0.0.1:51088
- - -
I opened the port 51088.
Is there anyone who met the same problem?
Is there any special settings for Windows Sever 2012??

Regards, :mrgreen:

Re: See message via browser in local

Posted: Fri Mar 17, 2017 11:07 am
by saitok
Hi,

I found when I launch Switch Watchdog as a service, I run into this situation.
The URL field of the browser is fixed like this.

http://127.0.0.1:51088/auth?username=Ro ... I+IkQhDxg=

Is it related to permission to launch Switch...?

Re: See message via browser in local

Posted: Mon Mar 20, 2017 12:35 pm
by sander
I'm running the same configuration as yours and don't suffer with these problems.

I did not change the Watchdog Service, and the service is set at 'Manual' start type over here. The Switch Watchdog shortcut is placed in my startup folder, I'm not sure if I did or the Switch installer did, but it's working perfect :)
Image


Running;
Switch 13.1
Windows Server 2012 R2, Dutch

Re: See message via browser in local

Posted: Tue Mar 21, 2017 11:08 am
by saitok
Thank you Sander!

I restored the Switch preferences and the SwitchWatchdog shortcut became to be placed into the Windows startup folder.
But it isn't fixed.

I guess when the node.exe in C:\Program Files (x86)\Enfocus\Enfocus Switch 13\SwitchWebService doesn't make the port 51088 LISTENING, I can't connect to the message even though in local.
But I can't know the reason of this.

I'll continue to investigate...

Regards,

Re: See message via browser in local

Posted: Tue Mar 21, 2017 3:11 pm
by sander
Strange. Any security software running?

Euhm, get yourself TCPView.exe and see if it's actually doing something?

Image

Download: https://live.sysinternals.com/Tcpview.exe

Re: See message via browser in local

Posted: Wed Mar 22, 2017 12:02 pm
by jonasy
Are you using a proxy in your company? If so, then it might be necessary to set it up to bypass the proxy for local addresses. You can find out how on this page:

https://www.enfocus.com/en/support/know ... 0014hlZAAQ

If it doesn't work out, then you can contact Enfocus Support via the portal:
https://www.enfocus.com/supportportal

Re: See message via browser in local

Posted: Thu Mar 23, 2017 2:34 am
by saitok
Thank you Sander,

I didn't know this tool.
Looks like very useful !!
Actually, I can't go back to my office until next Monday.
I'll check the port state again using this tool.
And I think I'll try netsh winsock reset command I found at the following page.
https://gns3.com/discussions/can-t-conn ... r-http-127

Hi Jonasy,

Thank you for your advise.
We should do the proxy server settings onto our Switch server.
I'll check the bypass settings at the next chance.

I'll come back here bringing any results.
Thanks!! :mrgreen:

Re: See message via browser in local

Posted: Tue Mar 28, 2017 11:02 am
by saitok
Hi,

I'm using my Switch as a service recently.
So, the local SYSTEM account starts the Switch automatically when the machine is booted.
The node.exe launched by the SYSTEM looks like that it crashes just after launched.

After I changed the account to start the Switch to the built-in Administrator I usually log on with, I could connect to the Switch Message window in the local.
But from that time, the errors below happens repeatedly when I start the Switch Designer.
Failed to get apps info: [10061] Connection refused
Failed to check unassigned apps: [10061] Connection refused
Failed to install new apps: [10061] Connection refused


(Actually, I found that even though I have the SYSTEM start the Switch Watchdog service, I could connect to the Message after I changed the Switch Application data root in the Preferences. But it should be the way Enfocus doesn't recommend.)

Hmmm...
I wonder which way is the most safe for me. :?