WAN Config

  • Thread starter Thread starter James
  • Start date Start date
J

James

I am setting up a WAN, which I have never done before, and am a little
confused. If anyone can help I would be appreciative.

I have 3 sites with existing LAN's each is a duplication as far as the IP
range is concerned (192.168.0.1 / 255.255.255.0) but the Domain name differs
for each site.(one.domain.com / two.domain.com / three.domain.com)

Our telco has provided a private link between sites. Each site now has a
router (IP's 192.168.0.1 / 192.168.1.0 / 192.168.2.0) I can ping each
router from our primary site. However, the telco says that the rest is up
to me.

It is all very well being able to ping a router, but I need easy access to
the machines on the other side. I had expected that when the telco finished
their bit I would be able to go into Networking and see the other two
domains listed. Where to from here?

The 3 LAN's are not huge. Would I be best to change the mask we use from
255.255.255.0 to 255.255.0.0 at all sites and remove any address duplication
? Will this make the routers transparent ? What are my options, and which
would be best?

Thank you

Regards, James
 
Don't think you have any realistic options except to change 2 of the
internal subnets. Basically, there is no easy way to route pakets from the
192.168.0.0 network to the ....uh, 192.168.0.0 network. For browsing you
will need WINS and even then, you may have problems.

Doug sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
Thank you Doug.

I am mapping out IP changes now. The two smaller offices don't have any
more than 30 machines each so I thought this might be a good move whilst the
WAN is new anyway. I wasn't sure on what can be achieved otherwise (ie with
routing tables) . I am also assuming that the LAN's on either side of the
router will become visible with the addressing changes, or do I need to do
more ?

Regards, James
 
Once each network has a unique address range (ex: 192.168.1.x/24 192.168.2.x/24 192.168.3.x/24) then if all routers have static routes defined to let them know how to talk to one another then you should change your default gateways to be those of the subnets router. You can use DHCP (if it’s in use) to simplify this on the clients, the servers should have their IP information configured statically.

Since these are separate domains you should think about how you want them to interact.

Are you going to set up trusts between them?

How is name resolution going to be handled?

How is name resolution handled now?

If there are existing DNS servers what are their zone types?

Are the existing Domains Active Directory Integrated?

Planning and having a good understanding of how these separate entities are going to interact is very important. You may want to think about consolidating into one contiguous name space, weather you maintain child domains in one forest or use a single domain will be a consideration. It depends on your business model. Are these sites separate companies?

Remember your network topology should reflect your business model. Always plan a network that will work for you, not one you will be working to keep from bringing your business to a halt.

Ian Bagnald
MCSE:Security Windows 2000
MCSA:Security Windows 2000
COMPTIA A+
 
Once each network has a unique address range (ex: 192.168.1.x/24 192.168.2.x/24 192.168.3.x/24) then if all routers have static routes defined to let them know how to talk to one another then you should change your default gateways to be those of the subnets router. You can use DHCP (if it’s in use) to simplify this on the clients, the servers should have their IP information configured statically.

Since these are separate domains you should think about how you want them to interact.

Are you going to set up trusts between them?

How is name resolution going to be handled?

How is name resolution handled now?

If there are existing DNS servers what are their zone types?

Are the existing Domains Active Directory Integrated?

Planning and having a good understanding of how these separate entities are going to interact is very important. You may want to think about consolidating into one contiguous name space, weather you maintain child domains in one forest or use a single domain will be a consideration. It depends on your business model. Are these sites separate companies?

Remember your network topology should reflect your business model. Always plan a network that will work for you, not one you will be working to keep from bringing your business to a halt.

Ian Bagnald
MCSE:Security Windows 2000
MCSA:Security Windows 2000
COMPTIA A+
 
You might want to use higher numbers in the third Octet on all three
networks since probably 1 through 5 are heavily over used and you don't want
to run into the same problem in the future if you ever VPN to other
companies.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
 
Thank you.

All done. I have a small problem I can't seem to solve though. From the
192.168.1.0 and .2.0 networks, I cannot being a Win98 box I need to access
on the 192.168.0.0 network. I can ping the router and a several server that
are behind it. But not this machine I need to map drives on. I can readily
ping and use this machine within the 192.168.0.0 subnet.

Any ideas ?

Thank you

Regards, James
 
I was planning trusts between the domains on each subnet. I am using DHCP
and WINS on each subnet, which now need some work to allow for the new
structure. Although I have a DNS Server running I am still trying to get my
head around it.

What would be the pros and cons of consolidating ?

Thank you

Regards, James
 
Back
Top