Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cross domain routing through VPN

Status
Not open for further replies.

bigkeith

IS-IT--Management
Jul 27, 2001
36
GB
Morning all,
A little background info first.

Internally we have two domains which are linked via a vlan in a netgear switch (Domain A and Domain B). Both of our domains have their own Exchange server and file store, and obviously have different IP ranges. Each domain can access the servers on the other domain, with the help of a route on each client/server to and from the other domain. This setup has worked fine, until we merged the exchange servers into one on Domain A.
The problem we are now having is that the owner of the company uses VPN to remotely connect and receive emails from Domain B onto his PC at home. Since the merger we cannot get his client to talk to domain A, which now houses the exchange server. He can ping and access as far as Domain B, but not onto domain A. I have added a route to Domain A on the firewall on Domain B, but still no joy.

I hope this explains our problem, and hopefully someone can shed some light or indeed help us with this. If there is anything that I can add to clarify the problem or our setup then let me know.

Many thanks in Advance

Keith
 
it sounds like domain a doesn't have a return route for the VPN address pool.

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)
 
Hi unclerico,
Thanks for responding. I agree that is where I feel the problem lies, but where do I add the return route and to where. I have many options, as there is a fair chain of hardware along the route. I imagine I have to start at the router on the remote site and maybe daisy chain the routes right through to Domain A and back again, but there's a lot of room for error. I have attempted this, but had no great success. when you ping domain A from the remote client the packet gets lost in transit, and if I tracert the request it stumbles around the router prior to the firewall. This is owned by our ISP, but they insist the problem lies internal.

Unfortunately, I'm going to have to reverse the merger in order to get things working as they were on Friday night. This means undoing about 30 hours work :(

Regards

Keith
 
don't do anything drastic now ;-)

can you post a topology diagram so i can see exactly what you're dealing with here??

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)
 
Sorry, I'm afraid it's been decided to revert back to prior to the merger. The owner has insisted this happens as he is struggling without emails.

I'll have to come back to this at another date and attempt it again. I will post a topology here when I get the time and I'd apreciate any input for this (future) plan, but it's all hands to the pumps at the moment.

Many thanks for trying to help me.

Regards

Keith
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top