>I'd like to get some thoughts on how best to organize my network and projects.
>
>I have set up a server with Win 2003 Server. I have 2 laptops and 3 PC's. More PC's will be added soon.
>I also have multiple projects and code components across the laptops and PC's. I have installed VSS 2005 and SQL Server 2005 on the server.
>
>I would like to have only one base of code, and I'd like it all in source control. The problem is accessing my server when I'm not at home. If I were going to go to a client site and do some work there, assuming an internet connection I could connect to my server and check out any project components I needed. If I knew beforehand that I would not have a connection, then I would check out the components to my laptop beforehand and check back in when I got back to the office.
>
>One option is a web hosted source control service. I have an account at http://www.dynamsoft.com/ and it works well, but it's not on my server.
>
>I'm curious how everyone else is managing things.

So basically you have two scenarios:
1. Your away from base and have a network connection.
2. Your away from base and don't

In the first instance you have lots of options - if you have a fixed IP address at base (or even a relatively fixed address) then the simplest solution is to access VSS via IIS. I see Bill has mentioned having problems with this - but I've been using it quite happily for a year or so (in my case in reverse - when I'm working from home I access VSS at the clients site)

In the second case it's not the end of the world - .NET will let you operate in a 'temporarily disconnected' mode - i.e. check out, make changes and check back in when you next hook up.....