Multiple Locations, One Exchange server - TechRepublic
General discussion
September 29, 2000 at 01:46 AM
aphatmouse

Multiple Locations, One Exchange server

by aphatmouse . Updated 25 years, 7 months ago

I have a situation with a company that has offices in three states where No one seems to be able to properly log on from anywhere except the main office. They have a main branch in NH, and a satalite each in ME, and CT. They are all connected to NH via T-1 lines, with NH having a PDC/Exchange server and ME/CT each having BDC’s. Each location uses a different IP adressing scheme, so ME sees only ME, NH sees only NH etc. Every machine, regardless of location, looks to the one Exchange server in NH for email. It seems to me, that with this setup things have never been quite right. I have never been able to make any changes to users, servers etc. (even though I can see them) from any of the BDC’s and lately no one from CT/ME can log on- they get a no domain controler is availble to validate you type message. I can ping each state ok, so I know that all the routers are up etc. So here is my question….is this whole scheme set up wrong…if all three states are going to be on one domain, shouldn’t they all be using the same IP adressing scheme, DNS, WINS etc. with the exception of the Gateway address? or am I better off dividing each state into a seperate domain? If I set up trust relationships between the domains, I should still be able to have each state log into the one Exchange server, right? Even if I do this though, am I better off having all domains on the same IP Adressing scheme?

Thanks!

This discussion is locked

All Comments