PDA

View Full Version : Problem with Server Version rc2_20201


CPL42
13-03-2005, 23:01
Hi,

Is there a bug in the password file?

It seems as though if I change the default passwords for admin and superadmin, the login no longer works at all.

Creating users and passwords has the same affect.

Believe me I've typed the simplest passwords to test this out like : blahblahblah and it still doesn't work. I created a user with 3 letter login and 3 letter password and still didn't work.

BUT!!!! If I use the password generated at the time of first startup for the admin, it works fine. and I can get in and administer the server. But with the passwords gone bad, what's the use of touching anything.

I have to uninstall and reinstall to get back into the server admin using the default passwords.

I know the server is running because when I try to connect to it through the internet from another machine using the latest TS client on my network, the server name that i created comes up, but then the voice comes on and says "your connection has been terminated" because it couldn't log in.

Please help.

I will try going to go back to an older version and see if it does the same thing, but any help here would be appreciated.

Thanks.

CPL42 :confused:

m&m's
14-03-2005, 01:49
if you make new logins in the webadmin , log out of the default, and log in with the new befor you deleat the default or it may not take the new accounts , if i am understanding the situation

CPL42
14-03-2005, 06:56
if you make new logins in the webadmin , log out of the default, and log in with the new befor you deleat the default or it may not take the new accounts , if i am understanding the situation


Yes, that part is correct. That solved half my problem.

The other half now is that i can not log in from my client.

I am still "terminated" even when logging in with a server/admin user.

Any ideas?

I've forwarded UDP 8767, TCP and Telnet ports per the manual, and still get this error.

I'm at a dead stop, anyone?

CPL42

m&m's
14-03-2005, 07:00
I've forwarded UDP 8767, TCP <--- use UDP not tcp

CPL42
14-03-2005, 09:16
I've forwarded UDP 8767, TCP <--- use UDP not tcp

Ya, I did that.

I should have been more clear with my details:

Port Forwarded 8767 on UDP

I thought that was enough, but apparently it was not so I went ahead and

Port Forwarded 51234 on TCP
Port Forwarded 14354 on TCP

still doesn't work.

I tried running it on a 3rd computer on my network, accessing the server thorugh the internet, I get the welcome message, but the login still does not occur.

I triple checked the account locally and it's good.

Still stumped.

Thanks for all your help.

m&m's
14-03-2005, 23:13
Port Forwarded 51234 on TCP
Port Forwarded 14354 on TCP

are for remote admin use and are not needed by the server for clients to join !

try port fowarding 8767-8678 udp some routers close off the second port and if both the open port and close port are the same no port is open so set a 2 port range and test it