Topic: can't access server manager other than localy or by ssh (sam

[DS]

It seem to like only localhost access. I tried a lot of things, even getting my hands "dirty" and changed access policy, nothing seems to work. I added local network again as a new local network to try to access by https, swapped nics in the idea that it can be a problem of configuration and to allow it to reconfigure itself again, then I changed back. Everything else works. Except I need to restore it and I couldn't find a way to do it locally or by ssh. It is SME 6.0beta3. 5.6 worked perfectly.
I even tried to forward the port to local host, I am getting desperate.
Thanks.

[Michael Soulier]

DS wrote:
>
> It seem to like only localhost access. I tried a lot of
> things, even getting my hands "dirty" and changed access
> policy, nothing seems to work. I added local network again as
> a new local network to try to access by https, swapped nics
> in the idea that it can be a problem of configuration and to
> allow it to reconfigure itself again, then I changed back.
> Everything else works. Except I need to restore it and I
> couldn't find a way to do it locally or by ssh. It is SME
> 6.0beta3. 5.6 worked perfectly.

If all you need to do is access the server-manager from the public network, that is configured from the remote access panel like in 5.6. If you previously used the local networks panel to add server-manager access, that was incorrect, and opened far more than you needed.

Mike

[DS]

Sorry for being such a pest, but the problem is still here. I tried everything I could think of, from modifing http-admin config file to changing to swapped mode the NICs, from reinstalling to burning a new ISO. Everything fails. The daemon refuses to listen on any other interface except loopback (127.0.0.1), even if I added by hand local network. I am really puzzled by this and I had hopes that someone else had the same problem. I have good conectivity on both interfaces, everything seems in order, works fine, even the config for http-admin is ok. But still not working. Is there a reason why it can treat local network as external ? Somebody had this problem with other daemons ? Or, at least, can you tell me how to perform a restore using only ssh or the local access ? Thank you !

[Michael Soulier]

DS wrote:
>
> Sorry for being such a pest, but the problem is still here.

If you think you've found a bug, please email smebugs@mitel.com with a detailed report.

Cheers,
Mike

[Greg Farnham]

I have a similar problem (I think).

I can access SSH from local network, but not from IP I added as a local network.


I have SSH access set to private.
I can access SSH ok from local network.

Under Security>Local Network I added an IP w/ netmask of 255.255.255.255 the IP is a static IP provided by my ISP.

I tried to access SSH from static IP that I added as a local network, but I get connection refused.  Should this work?

It works ok if I set SSH access to public, but I would rather not do that for security reasons.

GDF

[Arne]

Have the same problem too, but one problem or idea strucks me .. It couldent be a firewall problem, to make access from the outside .. the server manager runs port 980, or what ... ??

[Arne]

It appeared to be a firewall problem.

It seems to be two way of doing it:

Step 0. Set up for remoote avccess at the server manager panel.

Alternative 1: Open (or forward) port 980 or port 981 for encrypted comunikations. If you have a router in front this will have to have portopening and forwarding of port 980 or port 981 (The last should be the bether.)

Alternative 2: Set up a ssh tunnel from the client to the server. Using thisl alternative will not require any portopenings or portforwardings exept for port 22. I am using a ssh tunnel now, and it works really great so I can get the graphical server-manager panel up to my local ( = remote) client on this adress (on the remote mashine): "http://localhost:980".

I think the port opening/forwarding solution would also had worked, but I havent tried it because I think the tunneling alternative works just great as there is no need for opening more ports in the firewall, and using ssh it is also all encrypted.