SBS 2000 / Server 2003 WAN

M

mfdc

New Member
Ok

If possible I would like someone to offer advice on the following;

a WAN, European wide, five servers running Server 2000 and above , Active directory, all servers running WINS & DNS. IP ranges are class C private, 192.168.0.xxx, 192.168.1.xxx, 192.168.2.xxx and 192.168.3.xxx

a standalone network, running SBS2000, ten clients, server running DHCP, 2 meg broadband connection. IP is a class C subnet 192.168.0.xxx (NB the conflict between the IP range above)

Problem: Both the WAN and the smaller network need connecting up to talk to each other, basically the smaller LAN becoming part of the WAN as a trusted domain.

The smaller LAN has had a dedicated ADSL line installed, along with a pre configured firewall/router on an IP address of 192.168.4.xxx. I intend to configure DNS on the server for the new IP range, configure a new scope using .4.xxx, renew all the clients, configure any static mappings etc and then configure interdomain trust.

Theres an issue I understand with interdomain trust on SBS 2000. Basically there isnt any! Is that right?

Any problems can anyone see?

Thanks
M
 
In theory this should work but i would recommend you do lots of reading into both's security settings first and ensure they will talk back and forth. I ran into a similar problem at school last year and after almost 2 days of beating my head on the wall we called the company and they had us change some major settings. Definitely back everything up first and then go for it, worst case you just revert it all back to how you had it.
 
thanks

SBS is designed for a single domain enviroment, so a multiple trusted push/pull multi domain enviroment is a no go, I know wont work. However, I know theres some work arounds, perhaps connect it as an extended cleint off one of the domains, (although I dont want to deplete my IP pool) and I know theres some hacks too! It was that angle I was after,

Im going to install Windows Server 2003 anyway and do a full migration on all the clients, shame they have to lose Exchange, but hey ho!
 
do you know what guys, doesnt matter. I've read the forum rules, I've posted over four extremley helpful (and certainley more accurate) answers to other posts to show willing & help other people out and all I wanted was to bounce a few networking/sever issues out with some knowledgable people. Can I presume then, that judging by activity on the forum and this thread alone, that no-one 'does' servers!? :-)

Sorry just expected a few more replies thats all -:mad: -
 
There are a few of us who actually work in the enterprise level. My first question is, do you have a budget? You could basically bridge both networks with a router, and not a too expensive one. Something around the several hundred dollar range would work.

Another way would be to set up a second DHCP server which would act as a DHCP gateway (sometimes call DHCP relay) which could be done with a cheap linux box, or again with a decent router.

So in theory you could have your one DNS server with AD running and then set up other remote locations to act as DHCP relay/gateways via WAN....

I think that is what you were asking I couldn't quite make it clear exactly what you are trying to accomplish.
 
You must log in or register to reply here.
Back
Top