Error when connecting to Plastic Server

[esthrim]

Hi, i have problem when connecting to the plastic server, the error said :

A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was suppplied: PLSTC_Server:8087 Plastic client can't continue and will be closed.

my network is using DHCP, and sometimes the plastic server ip address may change.

so i use server name rather than ip address. But when the plastic server's Ip address changes, it show the error.

Please help,

Thanks alot

[manu]

Hello esthrim,

the error is coming from the network layer, so I'm afraid there's nothing we can help with it.

Please check the router configuration and give a static IP to the Plastic SCM server.

[esthrim]

currently we working on it to get ip static for plastic server,

but meanwhile, is there any configuration that we can change, in the plastic client ?,

so we don't have to delete the workspace and then create new workspace again with correct plastic server's ip address ?.

Thanks manu.

[manu]

Ummmmm,

from Microsoft:

"Check the following: 1. Ping the remote host you were connected to. If it doesn't respond, it might be off-line or there might be a network problem along the way. If it does respond, then this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again). 2. Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step). 3. Ping your local router address. If you are on a serial connection, your local router is the IP address of the host you initially logged on to using SLIP or PPP. 4. Ping a host on the same subnet as the host you were connected to (if you know of one). This will verify that the destination network is functioning. 5. Use the tracert command at the command prompt to determine the path to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way."