Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Helps a little. I'm pretty lite on server stuff anyway. When you say >hardcoding my server's name into my hosts file along with the public IP how is that done, and is it on client, server, or both? >registering the server in DNS Do you mean the internet DNS at large, or the DNS stuff you find in NT/XP networking setup, and again, client, server, or both? Thanks again Dave A. On Tue, 2 Nov 2004 15:52:17 -0500, Matt Epstein wrote: >Hi Dave, > >I just got my remote access working recently over :sserver. I couldn't use >:sspi unless I VPNed to our corporate network. However, I am using my domain >account to authenticate because aliased my domain account into the passwd >file using: > >cvs passwd -a -D <domain name> <real account name> > > So you should be ok over sserver regardless of whether you use a cvs >username or a domain username. > >Regarding the servername issue, I was initially able to connect by >hardcoding my server's name into my hosts file along with the public IP >address I need to use to hit it from remote location. That way my CVSROOT is >exactly the same as it is when I am local to the server, but the system >would resolve it to the public IP address that I needed to use from remote >location. > >Eventually we ended up registering the server in DNS so that the name would >resolve to the correct IP address so now I just use cvsserver.mydomain.com >as my servername in CVSROOT. > >I hope that helps a little. > >-matt > > ><david.arendash at manyone.net> wrote in message >news:mailman.2403.1099426662.21094.cvsnt at cvsnt.org... >> So I finally got CVSNT + Tortoise working for me on my LAN, >> where I can specify the computer's name as the server name, >> ex: :sspi:CVSserver:/cvsnt/archive >> >> and connect, since I have the same user/password on both client >> and server. >> >> Now I want to access remotely. I opened ports 2401 and 2402 in my >> firewall to that servermachine. I can obtain the mostly-static IP >> address. But when I go remote, I only know (for example): >> >> :sspi:123.321.255.64:/cvsnt/archive >> >> In other words, no domain or machine name. >> >> Suggestions? Would a different protocol work? I tried ext and sspi >> and pserver, they all fail, generally saying 'server actively rejected >> access' >> >> Thanks >> Dave A >> >> "Some men see things as they are and say why? I dream things that never >were and say "Why not?" -- Robert Francis Kennedy >> >> "Never doubt that a small group of committed people can change the world; >> indeed, it is the only thing that ever has." >> --Margaret Mead, anthropologist >> >> > > >_______________________________________________ >cvsnt mailing list >cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook >http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs > "Some men see things as they are and say why? I dream things that never were and say "Why not?" -- Robert Francis Kennedy "Never doubt that a small group of committed people can change the world; indeed, it is the only thing that ever has." --Margaret Mead, anthropologist