[Cvsnt] named pipe error 53

[Ian Epperson]

We couldn't get ours working over named pipes at first because of a WINS
hiccup.  Setting the offending machine to get a DHCP address from our
WINS/DHCP server, then rebooting the offending machine solved this.  The
ntserver protocol seems spotty to me, and apparently doesn't work over the
Internet, so it's useless to us.

After evaluating clients, we settled on using TortoiseCVS 0.44, so we can
only connect with the pserver protocol anyway.  This works fine, even
without WINS.  Later versions of Tortoise support the SSPI protocol, which
is what we'll use after a later Tortoise release stabilizes.

Hope this helps.

-----Original Message-----
From: massey at rmci.net [mailto:massey at rmci.net]
Sent: Tuesday, May 14, 2002 9:09 AM
To: cvsnt at cvsnt.org
Subject: [Cvsnt] named pipe error 53


Running Win2K Server with the latest cvsnt release. I can connect localy
but when I try to connect remotely I get

Couldn't connect to named pipe on remote machine: Error 53

I thought it was my firwall so I added the port and IP address of the
remote machine but still get the same error.

Clues? Hints? Would be nice<G>

Cheers

M;)



_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt