Windows Forum

Ask something
Discussion Locked

Two IP subnets in one Domain

0 helpful
6 replies

by akwok 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We were connected to the Internet through a Leased Line. Within our LAN, I used private IP (192.168.0.X), but some machine on the network were using real IP, such as the newly setup Win2K servers and few of the workstations. After AD services have been set, all workstations using private IP can't login to AD. I don't want to assing real IP to those workstations, and this is impractiable to assign all workstation with real IPs.
How can I make all workstations and server can be login to the domain regardless what kind of IP addresses are using?

6 replies

by mpdcsup

Sounds like you aren't routing the private address space properly.

If that is the case, you need to do one of the following:

Assign one of the private addresses (192.168.0.zzz) to the AD server so the clients can see the server as part of their subnet.

Or, configure routing on your default gateway to pass 192.168.0.zzz traffic to the public address space subnet.

by mpdcsup

Address translation is just one solution to a problem you haven't even identified as having. If your local workstations can't see your local servers, your two subnets aren't talking.

Details of your particular environment are required to make further recommendations.

If you use a Proxy server, you'll only want one server (the proxy) to have a public address. If you don't want your clients to have Internet access then routing between the private and the public subnets vs. multi-homing the public hosts would be appropriate under certain cabling constraints and/or for mostly even in-house traffic and medium levels of upstream and downstream Internet traffic. You'd probably go with the latter when your servers are pounded from both in-house clients and Internet requests.

by acurrin

You must be using Network Address Translation to route the private IPs to the Internet.

The correct way to handle the IP addressing would be to give the servers static private IP addresses and then to add static address mappings to the router that is handling the address translation. Then the router will pass the packets destined for the public address to a specific private IP address and your workstations will be on the same network as your servers.

In other words, the router accepts packets for the public IP numbers and routes them to the appropriate private address. If you don't manage your router, ask your ISP to configure it for NAT and to create static mappings to certain IP addresses.

This discussion is closed to new replies.