Direct Connect Servers

I need help connecting two Windows 2003 servers together direct using the second NICs. What am I doing wrong?

Here is what I've got. Two Win 2003 R2 servers, one set as the domain controller, DHCP, DNS, and to run a management database. The second to run IIS & terminal services. IIS & TS not installed yet.

The domain controller is setup on a name.local domain and on the local network (192.168.0.x). The IIS server (is not on the domain) is connected to the Internet with a public IP address (63.x.x.x).

I have the 2 servers directly connected on their second NICs on network 192.168.7.x.

I added a Reverse Lookup DNS entry for the IIS server with the public IP.

What I need to accomplish:
1. Connect the IIS server to the domain. I have not been able to do this yet. Does not see the DC.
2. Direct connect the servers together using their second NICs.
3. Be able to ping IPs and names between servers on both NICs.

Currently I can ping both IP & name from the DC to the IIS server on both NICs. I can only ping the local IP on the DC from IIS server on the public NIC. I cannot ping either IP or name from the IIS server to DC on the direct connect NIC.

Any help would be appreciated.
Thanks

 

To start with, for the IIS server to connect to the domain and work correctly, it needs to have it's DNS set to point at the AD server. See this FAQ post in the server forum:

http://www.windowsbbs.com/showthread.php?t=67193

Secondly, it is worth asking why you are setting up the two servers this way. It looks like you are configuring the system so that users on the internal network will have this path to follow to access the internet:

user ---> AD server ---> IIS server ---> internet

If that is correct you have three networks and at least two routers to configure:

• Network 1 - 192.168.0.0, internal network
• Network 2 - 192.168.7.0, network between two servers
• Network 3 - 0.0.0.0, the internet
• Router 1 - The AD server - need to route traffic between 192.168.0.0 and 192.168.7.0
• Router 2 - The IIS server - routes traffic between 192.168.7.0 and external
• Router 3 - You don't say how the IIS connects to the internet, but unless it has a modem and therefore a direct connection, there is another router and network (between this router and the IIS server) to manage

The key point is that this means you have to allow packets to pass through the AD server, either via proxying (with ISA for example) or routing. That's additional complexity that isn't doing an awful lot for you.

If the IIS server is acting as your main gateway to the internet, connecting it directly to the 192.168.0.0 network will be a lot easier to set up.