Problem With Two Connections. One cancels the other one out.

[blanski]

Ok, big problem that comes out of no where.
The server is an Windows Server 2003 IIS Web Server. It has two NICS.
One is a connection for the Local Lan and the other one is the internet
connection.
This setup has been working fine for months, if not years.
However, today it started malfunctioning with a bug that I've already
experienced on other servers but have never been able to figure out.

The external URL refuses to accept an incoming connection over the
internet. However, if I go into the server's network connections and
DISABLE the Internal LAN connection, the server accepts incoming
connections over the internet connection again.

If I reenable the Local Connection, it stops working.

Now this is a problem because I can't leave either connection disabled.
If I disable the local LAN the website works but the server can't
communicate with the other local servers (databases) on the LAN. If I
enable the local LAN, the internet connection stops working and no one
outside the LAN can connect to the webpage.

Help!

 

[Doug Sherman [MVP]]

Several possibilities, but most likely:

1. Make sure the LAN NIC does not have a default gateway configured. If
your internal LAN is routed, use static routes.

2. Right click My Network Places and select Properties. Click Advanced -
Advanced Settings. Make sure the LAN NIC is at the top of the binding
order.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

 

[blanski]

I think you were correct on #1.
It's working now! Thanks,

Quick question, are there any side-effects to removing the default LAN
gateway?

 

[Doug Sherman [MVP]]

Generally - no. No matter how many gateways you configure, Windows will
only use one of them unless and until it fails.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

 

[blanski]

Doug,

I have noticed a problem. Because it doesn't use our local gateway, the
server takes a long time logging onto a domain account. Specially on
the "Applying your personal settings" step.
Is there anyway to remedy this? Or will I just have to live with it on
the servers?

 

[Phillip Windell]

I have noticed a problem. Because it doesn't use our local gateway, the

All gateways are local. A gateway *must* be in the same subnet as the Nic
that uses it,...which qualifies it as local.

server takes a long time logging onto a domain account. Specially on
the "Applying your personal settings" step.
Is there anyway to remedy this? Or will I just have to live with it on
the servers?

Of course you have to have only one Default Gateway as we were saying,
but....
The Nic that faces the AD DNS Server must be in the top of the priority in
the bindings.
Properties of Net' Places
"Advanced" from top Menu
"Advanced Settings..." from the dropdown menu.
Make adjustments in the upper box by using the side arrows.
The "Applying your personal settings" are retreived from Active Directory
during login so good clean "unconfused" connectivity to the AD/DNS is
critical.

 

[blanski]

What I meant by local was the LAN. SOrry about the confussion.
This seems like it's going to work. Thanks!