Incorrect Password?

[Ron]

did you add your ip address to the allowed address list ? If you don't it says that the password is incorrect.... ( little misleading )

[Ron]

Change the ID string back to the original,..

"TCP/IP server" without quotes.

[Ron]

The TCP/IP client works just fine.

Make sure that you have

- In the hardware plugin ( server ):
* ID set to the default "TCP/IP server"
* Compatibility mode off
* Silent mode off
* Added the connecing pc's address ( add it explicitly if problems with 0.0.0.0/0
* Actually enabled the plugin ( dis-and enable the plugin after changes )

- The action plugin:
* Password correct
* Address correct
* Port correct
* Firewall disabled

etc etc etc


<font size=-1>[ This Message was edited by: RonB on 2002-02-08 20:17 ]</font>

[dbroome]

I'm trying to use the TCP/IP Server and either the console.exe program OR the TCP/IP client. Both return Incorrect Password. I can use telnet just fine.

The client dll is version:
Thursday, October 11, 2001, 7:34:04 PM

and the server dll is version:
Friday, August 31, 2001, 9:37:16 PM

Could this be a version compatibility problem? I believe both are the most recent. Any other ideas? I KNOW the password was entered correctly each 100 times I tried it :smile:

[dbroome]

Thanks for the thought, but unfortunately I have triple checked that, and have also added the 'all connections' string from the help file.

Here are my settings on the server (ip 192.168.1.103):
TCP/IP server only hardware checked
ID String: 1
Port: 1024
Password: 111
Allowed Clients: 0.0.0.0/0
192.168.1.100
Quiet Mode: unchecked
V1.x Compatibility: unchecked

and then the command line string I am sending (from ip 192.168.1.100):
console 192.168.1.103 1024 111 OLOFF (where OLOFF is the command).

Client is an XP machine and server is a Win98 machine.

Any more thoughts?

Telnet works like a champ unser these settings

[dbroome]

Okay, I did that and now it works from console.exe, but only if the 0.0.0.0/0 is allowed. When I remove that, it doesn't work even though 192.168.1.100 is still in the list.

The TCP/IP Client 2 from Girder doesn't work either way.

Some progress is better than none, though!

[dbroome]

Well, after much frustration and trying everything, I decided I would start over from scratch. After deleting Girder from both machines and from the registry, I set it back up (after re-downloading the zip file) on both machines and it is now working with the exact same settings it wasn't working with before.

Other than a corrupted setting or file somewhere, I have no other explanation. I'm not touching anything now that it is working, though :smile:

Thanks for offering your prompt assistance!