Server 2003 networking HELP!

[abernut]

Here is my situation.

Our company has a office in Virginia. Our main office is in Jacksonville FL.

Jacksonville:

T1

Cisco 2811(public IP on ser port, LAN Ip on eth port)

Watchguard Firebox X700 (Firewall and Controls VPNs)

5 3Com switches(in process of upgrading to Cisco Switches)

4 Windows 2003 Servers

60 users that are part of a Domain.

LAN=172.28.159.0

Virginia

Modem/Router(managed by local ISP)

Watchguard Edge(Firewall and Controls VPNs)

2 unmanageable switches

5 users that are part of a workgroup

LAN=172.28.158.0

What I would like....Is to be able to access the computers in Virginia from here in Jacksonville. Both sites have public IP's. I am able to log into the WatchguardEdge in Va from here in Fl.

I know that I will need to set up a VPN between the two locations.

How do I access the PC's in Virginia if they do not belong to a domain.

Thank you for your help

[fizban2]

Once you create the VPN between site it should be as easy as creating routes across your switches for the different subnets and then adding the remote machines to your domain. big down falls are going to be that the remote group is gonna have a terrible domain experience depending on the connection between the sites, no DC or DNS means all requests are going back out across the WAN to your main office. that will eat bandwidth and cause a not so happy user experience for thos in the virginia office. can't really justify a DC and DNS server for 5 poeple though, you will have to test it out and see what experince they will get

[Stoic Joker]

What type/level of access to the machines in VA do you need? Shares? RDC? The VPN should handle the routing for you e.g. any packet for target network X will be stuffed into the tunnel and pop out "there" (Tis their nature). So if the 5 machines in VA are statically addressed you could just use their IPs. Or setup a WINS server in FL and have them register with it.