Two NICs - Two Networks - No Clue



  • 1. QB180410 also for Windows Server 2003?
    Hi, I am experiencing a growing problem with PATH environment variable max length (1023) being too short - even after truncating all to 8.3. The abovementioned hotfix does not mention Windows 2003. How do I increase the PATH environment variable limit to 2048 characters on Windows Server 2003? Regards Morten Ross
  • 2. Exchange Info
    Hi All, I am new to Exchange 2003....:). I have a home network consisting of 3 Server2003 servers and, exchange is installed on one of these. My question is when i create a new user in AD the option to create a mailbox does not appear, what do i need to install for the AD exchange options to appear and, would the S/W be on the disk i have? Also when a new mail box is set-up how can i navigate to check the users mailbox. -- Flinty
  • 3. 2way trust question
    Hi, I have a 2way trust between an NT domain and a Win2003 domain. It got damaged somehow and I am recreating it. If on the Win2003 side I have more than one domain controller, do I have to create the trust on both? The reason I ask is because the NT side is seeing one server in the Win2003 domain but not the other. Thanks! --Randy Starkey

Two NICs - Two Networks - No Clue

Postby SmVyZW15IENyb2NrZXR0 » Sat, 28 Mar 2009 02:10:15 GMT


Hopefully I will make this concise. I'm setting up Server 2003 to function 
as a GhostCast server (PXE). I would like this to be completely separate from 
our Active Directory network as the Ghosting process adversely affects 
traffic.  Yet, I would still like to be able to access the WWW through our AD 

I've currenlty got two NICs in the server with the IPs hard-coded. One NIC 
is connected to a switch for the Ghosting and the other NIC is connected to 
the AD and cannot access the WWW.  What am I doing wrong? 

If anyone could point me in the right direction, I would greatly appreciate 


Re: Two NICs - Two Networks - No Clue

Postby dontinou » Sat, 28 Mar 2009 03:41:53 GMT


You have a routing problem.  Remove the default gateway setting on
your Ghostcast NIC.

Re: Two NICs - Two Networks - No Clue

Postby SmVyZW15IENyb2NrZXR0 » Sat, 28 Mar 2009 03:51:03 GMT

I needed to assign a DNS server to the AD NIC... oops! :( 

But thank you for taking the time to respond. Onward to Ghosting... I hope. :D

Re: Two NICs - Two Networks - No Clue

Postby Anthony [MVP] » Sat, 28 Mar 2009 16:07:40 GMT

Glad you fixed the name resolution.
I'm not sure why you would need two NICs for this though. Why not just put 
the server on the VLAN where you want the PXE service, and route between the 
two networks?

Similar Threads:

1.two nics - two networks

I have a windows 2003 server with one nic (192.168.100.x).  We just 
purchased a second company that's in our building.  Can I add a second nic 
and configure it to there network ip scheme (192.168.25.x) so that I can 
share one server?  I want to share the server, just not the information on 
the server.  Will either of the networks be able to one another if I don't 
bridge the networks cards?  Thanks for any help you can provide.


2.Server 2003 two nics two networks

We have multiple servers (2003) with two NICs.  In each machine, one
NIC is configured with a public IP and one with a 10.x.  Our lab
machines are all on the 10.x network.  The idea is that the lab
machines communicate via the 10.x to our servers.  However, they are
also supposed to be able to connec to the Net.  They go through a
router that has a private and a public interface for this purpuse.
However, I am finding that my servers are getting to portions (if not
all) of my public network via their private interfaces, through this
router, and on.  The effect - my router "poisons" my campus router such
that other computers on my public network cannot see my servers.  I
believe that what happens is that a computer on the public network goes
through our campus router to get to the server's public IP but the
campus router reports the MAC of my private router - it then discards
the traffic.  Anyhow, my assumption was that with any Windows Server
machine with two NICs with two networks would logically say: if this
packet is destined for 10.x go out my NIC with that network address.
If this packet is destined for a public IP go out my NIC with a public
IP address.  Is this logic wrong?  If so, what is the reason?  If my
logic is correct, what would cause my servers to violate this logic?  I
am more than willing to read whatever necessary if someone wants to
simply point me in the right direction.


3.Servers with two NICS and two networks

I have 8 servers with 100 desktops attached.  The servers connect to a 1gb 
switch that feeds all the desktops.  There is a firewall attached to the 
switch that provides Internet connection.  All pretty standard stuff = IP is to with mask of   

I have a tape drive in one server that backs up data from the other servers. 
 Since all the servers have two NICs, I was hoping I could setup a separate 
address range for those NICs and let the backup use that NIC and not flood 
the other with traffic.  

I can set the second NICs to be range with mask of  I would put in a new 1gb switch that just connects the second 
NICs (switch is cheap enough and no need to burden other switch with VLANs).  

What would I need to also configure on the servers so it knows that traffic 
destined for the other servers use the 172.16.x.x range and not the 10.10.x.x 
range?  What other settings do I need to know about?  

Is this config going to make a difference in inter-server communication 

4.Two NICs / Two Networks / One Machine

Here's the situation:  I have both DSL (pokey 800k) and Cable (2500k, usually) broadband modems in my SOHO.  I'd like to have both of these hooked up, not to run in a "Dual WAN" mode, but in an "either/or" mode

Is this possible

5.Two NICs And Two Separate Networks?

Question about a proposed office network.... All Windows XP systems

Network 1:
 Cable Modem ---> Router / Firewall ---> 3Com Hub ---> NIC #1 In
Machine (TCP/IP & DHCP)

Network 2:
 3Com Switch  ---> NIC #2 In Machine (IPX/SPX & Set IP Address)

I was told running a different protocol such as IPX/SPX on the second
network would make it more secure, is this true?

I understand that the PC's still are connected to the internet on
network 1 but wouldn't it be more secure since network 2 isn't
directly connected to the internet and in order to access network 2 a
hacker would have to go through the firewall and then though the

The server will be on network 2 and will not need internet access. 
One would think that since it is on a separate network it would be
more secure than being connected directly to network #1

Any ideas?

6. Two NICs & Two Separate Networks?

7. Two NICS, Two IP Addresses - ONE SERVER NAME

8. Two nics, two ISP's



Who is online

Users browsing this forum: No registered users and 28 guest