Hello,
I have a computer that has two NIC installed on it. I want to use one NIC to use the DSL line for the Internet. I want to use the second NIC to use the private network. The issue is that, the DSL gateway is different from the private network. When I setup the NIC, both NIC cards pulls the correct IP address of what they need to be. The problem is when I log into the domain, it takes forever to log in. It just sits there with the screen "logging in" or something like that. After two minutes, it logs me into the machine. I'm able to then browse the Internet using the DSL NIC. Just wondering if any of you smart computer geniuses have solution to using two IP's on two NIC's with different gateways. I was thinking about the "Teaming Driver", Load Balancing, or bridging.
Thank you all in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
It sounds like you are trying to setup ICS on your machine...??? When you enable ICS, your internal NIC will act as a gateway, and recieve a static IP of 192.168.0.1, while your external NIC should still get the dynamic address from your dsl router. Then of course, you must setup your network to reflect the changes.
Check out this article:
http://www.jsifaq.com/subg
Still, send the info requested so we can look at it a little closer.
FE
BTW: Is this machine a DC? It is not advisable to setup this configuration on a Domain Controller.
Read this:
http://www.jsifaq.com/SUBE
Yackko,
Your login delay sounds like a DNS problem.
If you've installed and configured DNS then verify that the system can resolve the local domain that you are logging into. It is also recommendable to have your clients use that DNS server only and configure it to forward non-local requests to the ISP. ICS is not recommendable because it has built in DNS forwarding which has to listen on the same port on which your DNS server should be receiving queries. You can configure NAT through Routing and Remote Access. Alternatively, you can run ICS on a different machine, but its probably not worth it as you dont gain any special functionality.
Regarding gateways, DawidS is right, you shouldn't have two gateways configured unless you have more than one internet connection. This will cause routing conflicts for your server and possibly loss of internet connectivity - the server wont know which gateway to use and if the internal gets favored, outbound requests will never reach the internet.
Thank you for everyone's help. Just to clarify some stuff of what I'm looking for. The machine is running Windows 2003 with two NIC installed on it. The question of why I'm running two gateway is not my chance. Well one of them is. The internal network of course has it's own gateway. The IP is assigned to a VLAN that routes to the LAN. The gateway for the DSL is assigned by SBC. No way of changing that. I'm thinking of setting up a VLAN on the Cisco switch, then assign an IP that matches the DSL subnet. And then set the VLAN to the specific port. What do you guys think?
Instead of having two devices do routing, why not setup RRAS on the internet server and have it do both VLAN routing and internet routing? then you'd eliminate the need for two gateways and possibly simplify your configuration. The only drawback is that the server would have to have a NIC in each vlan.
How are you currently routing between vlans?
This is a corporate network. This switch is a core switch and is also communicating with other core switches. It needs to have access to the corporate network. How it works is, we have several VLAN that as assigned a subnet. I'm trying to prevent from having to make a config change on a switch in order to resolve the DSL problem. I can resolve the problem by creating a VLAN and assigning an IP that matches the DSL's IP that SBC gives us, but I was wondering if there is a simplier solution instead of making changes on the switch. The PC has two NIC cards that are pulling the IP's that they are suppose to pull. One NIC pulls the private network IP, and the other one pulls the DSL IP. The problem is when I log into the PC. It takes about two minutes to login (Windows 20003 Standard), but it does log in and I'm able to use the DSL to browse the Internet. The ICS looks interesting. May have to try that.
Trouble? It wouldn't be a day of fun and excitement in networking if you don't get into some type of trouble... :o)
Really does sound like an interesting problem. But also really hard to TS in a forum. Too bad we cannot come over and see it for ourselves.. lol, eh? But it still sounds like you are trying to use the ICS concept, but it just is not setup correctly.
Trouble? The days do get a little dreary without it, but.... I do so look forward to them... :)
" I can resolve the problem by creating a VLAN and assigning an IP that matches the DSL's IP that SBC gives us, but I was wondering if there is a simplier solution instead of making changes on the switch."
Well this is why I asked you how you are routing between vlans - being that each vlan is its own logical network, you must have some layer 3 device between them (or your switch has a routing engine?); my next question being why cant that device be the default gateway and just route any traffic which is not between vlans out to your internet gateway? (I'm guessing this is what you meant by having to adjust your switch configuration)
Another thing you might want to rethink is giving the internet server access to your vlans in the first place? Maybe have it do outbound only and put DNS etc somewhere else? (okay, so much for simplification...)
"The ICS looks interesting." -I think you're better off NOT using ICS (Internet Connection Sharing) for the reasons that:
- Your network requires a DNS server eliminating the need for ICS DNS proxy (just use forwarders)
- You dont need the ICS DHCP service
- You can configure NAT with RRAS (which provides much more configurability)
- ICS (if you are already using it) is probably causing your login problem due to bind conflicts (assuming that your dns server is on the same machine)
Okay, i'll stop assuming now... hope some of this helps... heh
Business Accounts
Answer for Membership
by: DawidSPosted on 2003-12-15 at 17:24:48ID: 9946181
Have you actually got 2 sets of gateways? one on the lan and one on the WAN (dsl) side. If so why?
If you only use the dsl as a gateway then your lan interface should have no gateway defined and you Wan interface should have the dsl ip as the gateway address.
Install dns on the server itself and specify 127.0.0.1 as the dns address on the LAN interface. None on the WAN (I think this is only allowed in 2K3)
The clients should have the LAN interface IP address as their gateway and dns addresses. (If you have problems with DNS resolution enable forwarders on the DNS server itself)
Can you write down all the setting of the network cards and dsl network...
Dns Server IP:
Wins Server IP:
DSL Gateway IP:
Lan IP:
Lan Subnet:
Lan DNS 1 and 2:
Lan Gateway:
Wan IP:
Wan Subnet:
Wan DNS 1 and 2:
Wan Gateway:
etc all the IP related info you can give.
ps. If you ping the servername on the actual server does it resolve to an internal or external address? If it does not resolve to the LAN side nic IP address you have a bindings problem and should fix this. (Go to network folder and on the tool bar at top click advanced > advanced settings and make sure the LAN interface is listed ontop in the connections box on that page, reboot if you change it.