Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: cnpoobear on November 05, 2007, 09:23:54 PM
-
I'm having trouble tunneling into SME server 7.2 via another computer on our network. The computer I am using is running XP SP2.
I've been running an older computer as a server and it is running SME 7.1. Never had any trouble finding it on the net, tunneling, etc..
I've installed the new version of SME on a newer computer with the intent of upgrading. When I put the server on line, all attached computers are able to get on line fine and see each other but are having trouble logging onto the server.
They either can't find it or aren't able to logon to any of the IBays.
The biggest problem is my inability to tunnel in from my work station. I've been using Putty and never any problem.
What are the differences between 7.1 and 7.2 that may be causing this?
Oh yea, just to be sure on of the network cards wasn't faulty, I went through the config and swapped them between local and internet. Both were able to log on to the internet via the modem and both routed the signal through the hub.
If someone could help me out here I would be grateful.
Dave
-
I've installed the new version of SME on a newer computer with the intent of upgrading. When I put the server on line, all attached computers are able to get on line fine and see each other but are having trouble logging onto the server.
There have been some posts about domain membership of network workstations having problems after a SME upgrade. If you're running in 'domain controller' mode you might try removing a workstation from the domain, then adding it back. (Sorry, I can't find any helpful links to back this up at the moment!)
The biggest problem is my inability to tunnel in from my work station. I've been using Putty and never any problem.
I use putty with no problems to do anything I want on SME 7.2.
There are some 'gotchas' in 7.2 regarding running server-manager over an ssh tunnel - you can no longer tunnel port 980, nor does it work to tunnel any local port to port 443 on the server. You must tunnel port 443 to 443 on the sme box. (This change is a side effect of the new cookie-authentication-token login capability in server-manager).
Be sure to check your 'Secure Shell Settings' in Security::Remote access.
Finally, if you selected 'private server and gateway' during setup, there are implications as to what services are open - you may have to manually change the 'access' mode for some services using config setprop <servicename> access (public|private)