How best to connect a remote Windows network to our own?
December 29, 2003 8:51 AM Subscribe
How best to connect a remote Windows network to our own? [more inside]
My company just purchased another, smaller company, and we want to make our (Windows 2000) network available to them at their remote location for purposes of e-mail (Exch. Server), Intranet, and file sharing. We've got a T1, but they only have a 128K ISDN line. What's the best way to accomplish this? VPN? Trusted domains? Smoke signals? I don't need details, just the overall approach.
I'm really more of a programmer than a sysadmin, but I know my way around Win2K Server okay; it's the large scale logistics that baffle me utterly.
My company just purchased another, smaller company, and we want to make our (Windows 2000) network available to them at their remote location for purposes of e-mail (Exch. Server), Intranet, and file sharing. We've got a T1, but they only have a 128K ISDN line. What's the best way to accomplish this? VPN? Trusted domains? Smoke signals? I don't need details, just the overall approach.
I'm really more of a programmer than a sysadmin, but I know my way around Win2K Server okay; it's the large scale logistics that baffle me utterly.
Take 2 old machines, turn them into firewall/vpns. You can find more info on this slashdot thread.
posted by madmanz123 at 10:47 AM on December 29, 2003
posted by madmanz123 at 10:47 AM on December 29, 2003
« Older I'm looking for a product that performs the same... | What's the best personal audio device for $150? Newer »
This thread is closed to new comments.
Any of those will work (smoke signals are a bitch to troubleshoot, though).
We use VPN and/or trusted domains for a few of our remote offices, but our most common solution is an IP tunnel from the remote office to a gateway router at the home office.
posted by mr_crash_davis at 9:27 AM on December 29, 2003