|
From: Cook, D. <dar...@ci...> - 2006-01-04 21:05:31
|
Hello, I was having the same issue with a new server we're trying to use, and I just solved the problem. The server.bat file had "set HOSTNAME=3Dlocalhost", which worked on my older NT 4.0 server but not on the brand new Windows 2003 server. Changing this to HOSTNAME=3D%COMPUTERNAME% (or you can just hard-code the name of the server) and it worked great, I was able to connect via the client from my local machine. :) Darren Cook Enterprise Data Services - Applications & Tools Cingular Wireless dar...@ci...=20 "I love deadlines. I especially like the whooshing sound they make as they go flying by." ~Douglas Adams=20 -----Original Message----- From: sup...@li... [mailto:sup...@li...] On Behalf Of Stefan Reich Sent: Friday, December 23, 2005 4:15 AM To: sup...@li... Subject: Re: [superversion] Connection with server Hi Willem, "Connection to server lost" is Superversion's translation for a=20 NoSuchObjectException. I found that a lost connection usually leads to=20 this exception, so I gave it a special handling. However, it is possible that the exception is also thrown for other=20 reasons sometimes. The only reason I can imagine off the top of my head=20 is a version mismatch between client and server. You could try updating=20 all machines to Beta 8c. In either case, you should have an exception stack trace in the log=20 panel right after the exception occurs. Can you copy & paste that for=20 me? (Copy function is in the context menu.) Cheers, -Stefan Willem Clements wrote: > I am having problems connecting to superversion servers. I have a=20 > server (v2.0 beta7) running under OS/2 and can connect to the server=20 > with a client running on the same machine. Whenever I try to connect=20 > from another local computer, I get the following message "Connection=20 > to server lost, please reconnect" (Client beta8c under Fedora linux). >=20 > This also happens when I try to connect with the OS/2 client to the=20 > Linux server. The OS/2 machine doesnt have any firewall running, and=20 > the Linux machine has ports 20022 and 20023 open. >=20 > Even trying to connect with a client under windows with either the=20 > Linux or the OS/2 server gives the same results >=20 > Any suggestions? >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that=20 > makes searching your log files as easy as surfing the web. DOWNLOAD=20 > SPLUNK! http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > superversion-discussion mailing list=20 > sup...@li... > https://lists.sourceforge.net/lists/listinfo/superversion-discussion >=20 >=20 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick _______________________________________________ superversion-discussion mailing list sup...@li... https://lists.sourceforge.net/lists/listinfo/superversion-discussion |