Ok, Perhaps im just stupid...but I cannot get this to work properly for the life of me.
I have tried seemingly every possible configuration ~except obviously the one that works~ to get this to work properly. Ill try to make this brief :) We have an internally routed corporate network with a few dozen subnets...we utilize VPN for external and home users to dial into the network and that works like a charm. However once every year we put on a vendor show in dallas where we actually ship a terminal server down there to run various applications. We hook up a dozen workstations to an hub so they can communicate and log onto the terminal server. Now here is the tricky part. It is now required to connect that mini ~vendor show~ lan to our corporate network via vpn. Now everything ive read says this is possible. The Terminal server is connected directly to the internet and has a publicly routable IP. I can establish a VPN connection to the corprate VPN server. However my problems seem to come into play when dealing with the workstations. I have tried all options from configuring Internet Connection Sharing on the VPN connection, to setting up a Router 2 Router VPN server connection with demand dial interfaces. The ICS on the VPN connection allowed the workstations to talk to the corp network, but did not allow all applications to run ~outlook, client access, etc~. The Router to Router VPN connection only seems to allow the VPN server to talk to the entire network, and not the clients. Im about to pull my hair out on this, it should not be this difficult..or perhaps I should not be missing something this easy :/ Anyone ever do this? Ive read the R2Rvpn.doc on the microsoft site and setup the configuration to the tee. I guess Im running into a routing problem as I honestly dont see how systems in our corporate VLans will be able to route back to this remote site. ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
