The error you are getting indicates the one machine can not see the other.
Are you using an IP address or a machine name. this is an example of an
xinet file for cvs I have:

Service cvspserver
{
port = 2401
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/bin/cvs
server_args = -f --allow-root=/usr/local/FuseletRepository pserver
disable = no
}

Now for an explanation:

port is the port xinetd will listen on for any connections the the cvs
server. If it gets a request on this port then it will start the server and
pass on anything that it gets


socket_type is the type of socket the service expects you will use a stream

protocol is the type of packet the service expects, right now there is tcp,
udp, and Unix sockets, use tcp

wait indicates if xinetd should pause before starting the service, I believe
no should go here.

User is the user that the service runs as this would be the user that vista
runs under, I believe it is vista

Server is the command you type at the command line to start the server

I do not believe that you need any server_args but it is if there are any
command line arguments that you might use for the server

The important one is disable = no , I believe if this is blank it defaults
to yes so it disables the service

To check for connectivity first see if the machine can connect by the ping
Command ping <machine name> or ping <IP address> This can be done on a Win
machine with the command line. The next step would be to telnet to the
machine on the expected server port telnet <IP address or machine name>
<port number ( I believe it is 9200)>. This should get a connection, xinetd
is running correctly if you do not get connection refused by server.
The last part is troubleshooting for client server apps the xinetd is for
systems with xinetd. There is also inetd which has a different config file
format, this is inetd.conf you would add a line like this.

<servername> stream tcp nowait vista <path to command> in the
/etc/inetd.conf 







Thanks

Marc Aylesworth

C3I Associates 

AFRL/IFSE

Joint Battlespace Infosphere Team

525 Brooks Rd

Rome, NY 13441-4505

Tel:315.330.2422

Fax:315.330.7009

Email: [EMAIL PROTECTED]


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zeno
Davatz
Sent: Tuesday, August 02, 2005 12:58 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] xinetd configuration for OpenVista Server

On 8/2/05, Aylesworth Marc A Ctr AFRL/IFSE <[EMAIL PROTECTED]>
wrote:
> The broker service will not show as running until there is a connection.
> Xinetd listens for a connection and then starts the appropriate service
> (Daemon) to connect to.

Sure, but how can I debug the connection from the WindowCPRS GUI to
the OpenVista Server?

At the moment I just get the windows error:
Error encountered
Functions: connect
Error was: WSAEADDRNOTAVAIL

Thanks
Zeno


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to