Solved

Internet Sharing between domains

Posted on 2007-11-30
7
206 Views
Last Modified: 2013-11-30
I have two domains, A and B. Domain A connects to the Internet via a Sonicwall hardware firewall and all is well. I would like Domain B to connect to the Internet as well through the same Internet connection. Problem is that I have the two domain controllers using the 192.168.0.1 address on their network cards and they are on separate networks physically. I have installed another network card on the Domain B server to facilitate Internet connectivity via Domain A Internet, what else must I do to have this working? I can connect the second card from Domain B to the Domain A switch, assign an IP from that domain and Internet will work fine on the server only but the clients cannot connect unless I enable Internet Connection sharing on the connection. As you may be aware Microsoft will need the 192.168.0.1 address to enable ICS and I will end up with an IP conflict in that case. What should I do?
0
Comment
Question by:colinkhan
  • 4
  • 3
7 Comments
 
LVL 19

Expert Comment

by:darron_chapman
ID: 20381809
If the only connection between Domain A and Domain B is through that second NIC on the 2003 server connected to the Sonicwall, then it won't matter that the Internal NIC on Domain B's server has the same IP of Domain A's server as they won't physically be able to see each other.  If this is not the case and the servers are connected through the same switching network, then you will not be able use ICS to share the connection.

Do not use ICS on a network that:

• Uses static IP addresses
• Has a Windows Server 2003 domain controller
• Uses other DNS servers, gateways, or DHCP servers
http://support.microsoft.com/kb/324286

Instead of using ICS, you could use Routing and Remote Access.  This provides a much more flexible way of sharing out an internet connection.  http://www.jsifaq.com/SF/Tips/Tip.aspx?id=7351
0
 
LVL 1

Author Comment

by:colinkhan
ID: 20381988
The sonicwall has a switch built in which is connected back to domain A, this is where I need to connect the second NIC from Domain B to facilitate Internet access, problem is having the clients connect to this Internet connection from Domain B since by default the Internet will not be shared unless I use ICS, and this is where the IP problem comes in...
0
 
LVL 19

Expert Comment

by:darron_chapman
ID: 20382214
I really think the only way to get around your problem is to not use ICS and use Routing and Remote Access (NAT).  This will allow you to set the IP of the NIC to whatever IP you want.  The second NIC on your Domain B server will be on the same subnet as the sonicwall, but the first NIC can be set to whatever IP you want.
0
Network it in WD Red

There's an industry-leading WD Red drive for every compatible NAS system to help fulfill your data storage needs. With drives up to 8TB, WD Red offers a wide array of solutions for customers looking to build the biggest, best-performing NAS storage solution.  

 
LVL 1

Author Comment

by:colinkhan
ID: 20395100
Ok but how will the sharing be facilitated for Domain B? VIa routing and remote access as well?
0
 
LVL 19

Expert Comment

by:darron_chapman
ID: 20395540
On server B, when you set up routing and remote access, you choose which card will be your public (Internet) connection.  This will be the one facing the Sonicwall appliance.   And you will choose which card will be your private (LAN) card, this will be the one facing the computers on Domain B.  After you have it all set up, your computers on Domain B will need to be configured to use server B's IP as the gateway and the IP of course will need to be on the same subnet.  
0
 
LVL 1

Author Comment

by:colinkhan
ID: 20398403
Ok I have installed the Routing and remote access on the server. What do I do next? I have Internet access on the server via the second NIC which I configured to work with the Sonicwall appliance. Do I need to create a static route and if so on which interface?
0
 
LVL 19

Accepted Solution

by:
darron_chapman earned 500 total points
ID: 20398524
When you go into the Routing and Remote Access window, you right-click on your local server and click Configure and Enable Routing and Remote Access.  When you do that, a wizard will come up and step you through setting this up and will automatically create a static route.

Click Next
Click Network address translation
Under Use this public interface, chose the NIC facing the firewall
Click finish

Now you can go to the client computers and configure them as follows
IP: an IP on the same subnet as the servers first NIC
Subnet Mask: match what the sever has
Gateway:  IP of first NIC on server
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

If you need to start windows update installation remotely or as a scheduled task you will find this very helpful.
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now