Server

These properties can only be edited with the advanced user check enabled on the preferences page.

config-file: server 'address'
command-line: /s address

config-file: port 'number'
command-line: /p number

These are the standard TCP settings, they're like the coordinates on a map telling wconnect where connectd is. The host is the IP-address of the machine running connectd (or its name, if you have a nameserver) the port is just an abitary number; imagine these as a telphone number: the host is the area code and the port as the phone number.

The port is normally 800 (if it's anything else your administrator must have changed the port connectd is using). The host is presumed to be your DHCP server or your IP-gateway; it must be set explicitly if that isn't the case.

When wconnect opens the TCP connection to connectd, connectd sends a greeting (a message which says "Yep I'm connectd and its okay for you to talk to me"). But some protocols (like http) don't send any messages until the client says something, so at somepoint wconnect has to decide there's no connectd server at the other end of its socket and this timeout tells wconnect how long to wait for the initial greeting.

A slow DNS might neccesistate this being increased.

Wconnect doesn't know what icon to display until the server tells it. It's the initial state message which contains this information. If wconnect doesn't get a response quickly enough it suspects the server has hung and gives up.

This is really a "login timeout" (it will become that properly in wconnect 0.86) and a slow or bust server might neccesistate it being increased.

If this checked wconnect doesn't contact the the server when it starts, but waits for you to tell it to (via the 'Look for connectd' menu option). Similarly if connectd finds it's server has disappeared then it doesn't try and reinitiate the connection. This might be useful for laptop computers.

Normally, however, this is checked and wconnect tries to contact the server automatically when it starts up and when it loses contact.

Changes to this parameter only make a difference when wconnect is not looking for the server. If it becomes checked then wconnect starts looking for the server automatically. If it becomes unchecked wconnect cancels the next scheduled login attempt. If wconnect is looking for the server when this becomes unchecked, the login attempt is not cancelled (though of course no future login attempts are made).

This is just debugging information, but it seemed appropriate to put it collect it here with all the info about the server, rather than put it on the generic debuging page.