Topic: Remote access

[nigeltodd]

Is there anyway to have remote access to SME server-manager now?

With the closing of the localhost:980 loophole, it appears as though this is now impossible, unless there is another way. The webconsole contrib just runs a Java applet to produce the same result as a putty session.

Regards

"Remote Administrator"

[del]

Under Remote Access there is a heading called Remote Management, you can add the IP address of another network here and then log in from that network, all can be found in the administrator manual here:
http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter11#Remote_Access

Regards,
Del

[nigeltodd]

I appreciate that, but the network I wish to connect from can vary - especially if connecting via the internet. Any further thoughts? This woudl work fine if one were trying to access SME from the same spot every time.!

[shell]

What about VPN first?  Then you are considered local from where-ever...

[nigeltodd]

hmm - sound sfine - although I have not had  any success in the vpn stakes!

What is considered to be the best option for VNC, and preferably easy and reliable?

Next month I may have to try to support SME servers in Australia from East Africa!!

Nigel

[bpivk]

Is there anyway to have remote access to SME server-manager now?

With the closing of the localhost:980 loophole, it appears as though this is now impossible, unless there is another way. The webconsole contrib just runs a Java applet to produce the same result as a putty session.

Regards

"Remote Administrator"

Well it's a tedius task, but you can always login as admin and use server-manager from the console. Or just check the curent ip and enter it and then use the server-manager as you normaly do.

That's how i use it. Use ssh (with certificates off course) and then login as admin and enter the ip under Remote Access. Then just do what you normaly do and then delete the remote access entry.

[del]

hmm - sound sfine - although I have not had any success in the vpn stakes!

neither did I until I tried OpenVNP, there is a good thread on it here: http://forums.contribs.org/index.php?topic=33043.0
Alternatively I have used BPIVK's ssh trick which like he says is tedious but effective

Regards,
Del

[mmccarn]

Try tunneling port 443 instead of port 980 - then browse to https://localhost/server-manager.

[nigeltodd]

hmm  - just direct 443 to where?

if this works it will be great!~!

[mmccarn]

Code: [Select]

c:\path\to\putty.exe <smeserver> -P <sshd_port> -l root -L 443:127.0.0.1:443

Now browse to https://localhost/server-manager

Basically, replace 980 with 443 wherever you used to use 980.

Also, if you login using your old port 980 tunnel, just go back to http://localhost:980/server-manager after logging in and getting the error, and server-manager pops up as good as ever...

[nigeltodd]

Brilliant - thank you - am so glad there is still a loophole!

Cheers