Dual NICs on Server 2003 issue

I have a bit of a connundrum in configuration that I am unable to resolve
and would appreciate any help. On a new Windows 2003 server which is a
stand alone server in an existing AD domain we have 2 NICS installed. The
settings are as follows:
OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1

They are configured that way because we have people accessing the server
remotely to set up software so the outside NIC is connected to a router and
then a cable modem. The inside joins it to the domain where users are
accessing the server. We have a remote site that has VPN set up to the
site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the remote
site cannot ping the 192.168.87.153 IP - It times out. If I disable the
outside they can ping it without issue. I have changed the configuration
around, removing gateways, settng the INSIDE as primary etc but to no
effect. As it currently stands, If I disable the OUTSIDE, everything works
but the software developers cannot RDP in. If I enable it, the developers
can come in, local users can connect without issue but the remote site
cannot?

I assume that I might have to add a static route somewhere but just cannot
get the right configuration? If anyone has any expertise in this area I
would greatly appreciate the help.

We need more details to help. Since you setup two gateways, can we assuming you have two internet access? Or what do 192.168.1.1 and 192.168.87.1 connect to ?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"PGPhantom" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
I have a bit of a connundrum in configuration that I am unable to resolve
and would appreciate any help. On a new Windows 2003 server which is a
stand alone server in an existing AD domain we have 2 NICS installed. The
settings are as follows:
OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1

They are configured that way because we have people accessing the server
remotely to set up software so the outside NIC is connected to a router and
then a cable modem. The inside joins it to the domain where users are
accessing the server. We have a remote site that has VPN set up to the
site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the remote
site cannot ping the 192.168.87.153 IP - It times out. If I disable the
outside they can ping it without issue. I have changed the configuration
around, removing gateways, settng the INSIDE as primary etc but to no
effect. As it currently stands, If I disable the OUTSIDE, everything works
but the software developers cannot RDP in. If I enable it, the developers
can come in, local users can connect without issue but the remote site
cannot?

I assume that I might have to add a static route somewhere but just cannot
get the right configuration? If anyone has any expertise in this area I
would greatly appreciate the help.

You cannot have different gateway settings on the NICs. The only
default gateway setting should be on the outside NIC pointing to the router.
The gateway setting on the inside NIC should be blank.

"Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
news:O7%23%(E-Mail Removed)...
We need more details to help. Since you setup two gateways, can we assuming
you have two internet access? Or what do 192.168.1.1 and 192.168.87.1
connect to ?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"PGPhantom" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
I have a bit of a connundrum in configuration that I am unable to resolve
and would appreciate any help. On a new Windows 2003 server which is a
stand alone server in an existing AD domain we have 2 NICS installed. The
settings are as follows:
OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1

They are configured that way because we have people accessing the server
remotely to set up software so the outside NIC is connected to a router
and
then a cable modem. The inside joins it to the domain where users are
accessing the server. We have a remote site that has VPN set up to the
site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the remote
site cannot ping the 192.168.87.153 IP - It times out. If I disable the
outside they can ping it without issue. I have changed the configuration
around, removing gateways, settng the INSIDE as primary etc but to no
effect. As it currently stands, If I disable the OUTSIDE, everything
works
but the software developers cannot RDP in. If I enable it, the developers
can come in, local users can connect without issue but the remote site
cannot?

I assume that I might have to add a static route somewhere but just cannot
get the right configuration? If anyone has any expertise in this area I
would greatly appreciate the help.

The OUTSIDE Nic is the Internet. The inside is the local network which
connects via another gateway to a remote site that is on a 10.0.1.x subnet.
Should I: Delete the default gateway on INSIDE and then "route add 10.0.1.1
mask255.255.255.0 192.168.87.1" on the server?

What is the right syntax for the route add as I am connecting to the
192.168.87.x network INTERNAL then via the 192.168.87.1 gateway to the
remote site which is on gateway 10.0.1.1?

"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> You cannot have different gateway settings on the NICs. The only
> default gateway setting should be on the outside NIC pointing to the
> router. The gateway setting on the inside NIC should be blank.
>
> "Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
> news:O7%23%(E-Mail Removed)...
> We need more details to help. Since you setup two gateways, can we
> assuming you have two internet access? Or what do 192.168.1.1 and
> 192.168.87.1 connect to ?
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "PGPhantom" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> I have a bit of a connundrum in configuration that I am unable to resolve
> and would appreciate any help. On a new Windows 2003 server which is a
> stand alone server in an existing AD domain we have 2 NICS installed.
> The
> settings are as follows:
> OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
> INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1
>
> They are configured that way because we have people accessing the server
> remotely to set up software so the outside NIC is connected to a router
> and
> then a cable modem. The inside joins it to the domain where users are
> accessing the server. We have a remote site that has VPN set up to the
> site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the remote
> site cannot ping the 192.168.87.153 IP - It times out. If I disable the
> outside they can ping it without issue. I have changed the configuration
> around, removing gateways, settng the INSIDE as primary etc but to no
> effect. As it currently stands, If I disable the OUTSIDE, everything
> works
> but the software developers cannot RDP in. If I enable it, the
> developers
> can come in, local users can connect without issue but the remote site
> cannot?
>
> I assume that I might have to add a static route somewhere but just
> cannot
> get the right configuration? If anyone has any expertise in this area I
> would greatly appreciate the help.
>
>
>

Yes, some things like this.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"PGPhantom" <(E-Mail Removed)> wrote in message news:%23qo%(E-Mail Removed)...
The OUTSIDE Nic is the Internet. The inside is the local network which
connects via another gateway to a remote site that is on a 10.0.1.x subnet.
Should I: Delete the default gateway on INSIDE and then "route add 10.0.1.1
mask255.255.255.0 192.168.87.1" on the server?

What is the right syntax for the route add as I am connecting to the
192.168.87.x network INTERNAL then via the 192.168.87.1 gateway to the
remote site which is on gateway 10.0.1.1?

"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> You cannot have different gateway settings on the NICs. The only
> default gateway setting should be on the outside NIC pointing to the
> router. The gateway setting on the inside NIC should be blank.
>
> "Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
> news:O7%23%(E-Mail Removed)...
> We need more details to help. Since you setup two gateways, can we
> assuming you have two internet access? Or what do 192.168.1.1 and
> 192.168.87.1 connect to ?
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "PGPhantom" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> I have a bit of a connundrum in configuration that I am unable to resolve
> and would appreciate any help. On a new Windows 2003 server which is a
> stand alone server in an existing AD domain we have 2 NICS installed.
> The
> settings are as follows:
> OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
> INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1
>
> They are configured that way because we have people accessing the server
> remotely to set up software so the outside NIC is connected to a router
> and
> then a cable modem. The inside joins it to the domain where users are
> accessing the server. We have a remote site that has VPN set up to the
> site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the remote
> site cannot ping the 192.168.87.153 IP - It times out. If I disable the
> outside they can ping it without issue. I have changed the configuration
> around, removing gateways, settng the INSIDE as primary etc but to no
> effect. As it currently stands, If I disable the OUTSIDE, everything
> works
> but the software developers cannot RDP in. If I enable it, the
> developers
> can come in, local users can connect without issue but the remote site
> cannot?
>
> I assume that I might have to add a static route somewhere but just
> cannot
> get the right configuration? If anyone has any expertise in this area I
> would greatly appreciate the help.
>
>
>

That is pretty much what you have to do. The default route must be out
to the Internet. To route a particular set of addresses to some other
gateway you need to use static routing.

In the route command you need to specify the subnet, the subnet mask and
the IP address of the router which is the next hop towards the target. The
machine can decide which interface to use (because it has to be in the same
subnet as the next hop router).

To send all traffic for the subnet 10.0.1.0/24 to a router at
192.168.87.1 the command would be

route add 10.0.1.0 255.255.255.0 192.168.87.1

With that route in place, any traffic for an address beginning with
10.0.1 would be directed to the router at 192.168.87.1 through interface
192.168.87.153 (ie the inside NIC).

Remember to add the -p option to the command so that it survives a
reboot.


"PGPhantom" <(E-Mail Removed)> wrote in message
news:%23qo%(E-Mail Removed)...
> The OUTSIDE Nic is the Internet. The inside is the local network which
> connects via another gateway to a remote site that is on a 10.0.1.x
> subnet. Should I: Delete the default gateway on INSIDE and then "route
> add 10.0.1.1 mask255.255.255.0 192.168.87.1" on the server?
>
> What is the right syntax for the route add as I am connecting to the
> 192.168.87.x network INTERNAL then via the 192.168.87.1 gateway to the
> remote site which is on gateway 10.0.1.1?
>
> "Bill Grant" <not.available@online> wrote in message
> news:%(E-Mail Removed)...
>> You cannot have different gateway settings on the NICs. The only
>> default gateway setting should be on the outside NIC pointing to the
>> router. The gateway setting on the inside NIC should be blank.
>>
>> "Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
>> news:O7%23%(E-Mail Removed)...
>> We need more details to help. Since you setup two gateways, can we
>> assuming you have two internet access? Or what do 192.168.1.1 and
>> 192.168.87.1 connect to ?
>>
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "PGPhantom" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> I have a bit of a connundrum in configuration that I am unable to
>> resolve
>> and would appreciate any help. On a new Windows 2003 server which is a
>> stand alone server in an existing AD domain we have 2 NICS installed.
>> The
>> settings are as follows:
>> OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
>> INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1
>>
>> They are configured that way because we have people accessing the server
>> remotely to set up software so the outside NIC is connected to a router
>> and
>> then a cable modem. The inside joins it to the domain where users are
>> accessing the server. We have a remote site that has VPN set up to the
>> site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the
>> remote
>> site cannot ping the 192.168.87.153 IP - It times out. If I disable the
>> outside they can ping it without issue. I have changed the
>> configuration
>> around, removing gateways, settng the INSIDE as primary etc but to no
>> effect. As it currently stands, If I disable the OUTSIDE, everything
>> works
>> but the software developers cannot RDP in. If I enable it, the
>> developers
>> can come in, local users can connect without issue but the remote site
>> cannot?
>>
>> I assume that I might have to add a static route somewhere but just
>> cannot
>> get the right configuration? If anyone has any expertise in this area I
>> would greatly appreciate the help.
>>
>>
>>
>
>

This one keeps confounding me - I though I had the issue licked as
everything appeared to be working BUT ... When on the server now, people
using a domain log on have an issue as it cannot get authenticated? It
gives an RPC server unavailable error. The main AD server for the domain is
on 192.168.87.50. Do I have to add a route for that too? If so, what?

"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> That is pretty much what you have to do. The default route must be out
> to the Internet. To route a particular set of addresses to some other
> gateway you need to use static routing.
>
> In the route command you need to specify the subnet, the subnet mask
> and the IP address of the router which is the next hop towards the target.
> The machine can decide which interface to use (because it has to be in the
> same subnet as the next hop router).
>
> To send all traffic for the subnet 10.0.1.0/24 to a router at
> 192.168.87.1 the command would be
>
> route add 10.0.1.0 255.255.255.0 192.168.87.1
>
> With that route in place, any traffic for an address beginning with
> 10.0.1 would be directed to the router at 192.168.87.1 through interface
> 192.168.87.153 (ie the inside NIC).
>
> Remember to add the -p option to the command so that it survives a
> reboot.
>
>
> "PGPhantom" <(E-Mail Removed)> wrote in message
> news:%23qo%(E-Mail Removed)...
>> The OUTSIDE Nic is the Internet. The inside is the local network which
>> connects via another gateway to a remote site that is on a 10.0.1.x
>> subnet. Should I: Delete the default gateway on INSIDE and then "route
>> add 10.0.1.1 mask255.255.255.0 192.168.87.1" on the server?
>>
>> What is the right syntax for the route add as I am connecting to the
>> 192.168.87.x network INTERNAL then via the 192.168.87.1 gateway to the
>> remote site which is on gateway 10.0.1.1?
>>
>> "Bill Grant" <not.available@online> wrote in message
>> news:%(E-Mail Removed)...
>>> You cannot have different gateway settings on the NICs. The only
>>> default gateway setting should be on the outside NIC pointing to the
>>> router. The gateway setting on the inside NIC should be blank.
>>>
>>> "Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
>>> news:O7%23%(E-Mail Removed)...
>>> We need more details to help. Since you setup two gateways, can we
>>> assuming you have two internet access? Or what do 192.168.1.1 and
>>> 192.168.87.1 connect to ?
>>>
>>> Bob Lin, MS-MVP, MCSE & CNE
>>> Networking, Internet, Routing, VPN Troubleshooting on
>>> http://www.ChicagoTech.net
>>> How to Setup Windows, Network, VPN & Remote Access on
>>> http://www.HowToNetworking.com
>>> "PGPhantom" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>> I have a bit of a connundrum in configuration that I am unable to
>>> resolve
>>> and would appreciate any help. On a new Windows 2003 server which is
>>> a
>>> stand alone server in an existing AD domain we have 2 NICS installed.
>>> The
>>> settings are as follows:
>>> OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
>>> INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1
>>>
>>> They are configured that way because we have people accessing the
>>> server
>>> remotely to set up software so the outside NIC is connected to a router
>>> and
>>> then a cable modem. The inside joins it to the domain where users are
>>> accessing the server. We have a remote site that has VPN set up to
>>> the
>>> site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the
>>> remote
>>> site cannot ping the 192.168.87.153 IP - It times out. If I disable
>>> the
>>> outside they can ping it without issue. I have changed the
>>> configuration
>>> around, removing gateways, settng the INSIDE as primary etc but to no
>>> effect. As it currently stands, If I disable the OUTSIDE, everything
>>> works
>>> but the software developers cannot RDP in. If I enable it, the
>>> developers
>>> can come in, local users can connect without issue but the remote site
>>> cannot?
>>>
>>> I assume that I might have to add a static route somewhere but just
>>> cannot
>>> get the right configuration? If anyone has any expertise in this area
>>> I
>>> would greatly appreciate the help.
>>>
>>>
>>>
>>
>>
>
>

To add to this - I even added the 192.168.87.50 into the LMHOSTS file hoping
that would solve it and on the both INSIDE and OUTSIDE I have 192.168.87.50
as the primary and only DNS server as the 192.168.87.50 is the DNS server
for the domain.

"PGPhantom" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> This one keeps confounding me - I though I had the issue licked as
> everything appeared to be working BUT ... When on the server now, people
> using a domain log on have an issue as it cannot get authenticated? It
> gives an RPC server unavailable error. The main AD server for the domain
> is on 192.168.87.50. Do I have to add a route for that too? If so, what?
>
> "Bill Grant" <not.available@online> wrote in message
> news:(E-Mail Removed)...
>> That is pretty much what you have to do. The default route must be
>> out to the Internet. To route a particular set of addresses to some other
>> gateway you need to use static routing.
>>
>> In the route command you need to specify the subnet, the subnet mask
>> and the IP address of the router which is the next hop towards the
>> target. The machine can decide which interface to use (because it has to
>> be in the same subnet as the next hop router).
>>
>> To send all traffic for the subnet 10.0.1.0/24 to a router at
>> 192.168.87.1 the command would be
>>
>> route add 10.0.1.0 255.255.255.0 192.168.87.1
>>
>> With that route in place, any traffic for an address beginning with
>> 10.0.1 would be directed to the router at 192.168.87.1 through interface
>> 192.168.87.153 (ie the inside NIC).
>>
>> Remember to add the -p option to the command so that it survives a
>> reboot.
>>
>>
>> "PGPhantom" <(E-Mail Removed)> wrote in message
>> news:%23qo%(E-Mail Removed)...
>>> The OUTSIDE Nic is the Internet. The inside is the local network which
>>> connects via another gateway to a remote site that is on a 10.0.1.x
>>> subnet. Should I: Delete the default gateway on INSIDE and then "route
>>> add 10.0.1.1 mask255.255.255.0 192.168.87.1" on the server?
>>>
>>> What is the right syntax for the route add as I am connecting to the
>>> 192.168.87.x network INTERNAL then via the 192.168.87.1 gateway to the
>>> remote site which is on gateway 10.0.1.1?
>>>
>>> "Bill Grant" <not.available@online> wrote in message
>>> news:%(E-Mail Removed)...
>>>> You cannot have different gateway settings on the NICs. The only
>>>> default gateway setting should be on the outside NIC pointing to the
>>>> router. The gateway setting on the inside NIC should be blank.
>>>>
>>>> "Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
>>>> news:O7%23%(E-Mail Removed)...
>>>> We need more details to help. Since you setup two gateways, can we
>>>> assuming you have two internet access? Or what do 192.168.1.1 and
>>>> 192.168.87.1 connect to ?
>>>>
>>>> Bob Lin, MS-MVP, MCSE & CNE
>>>> Networking, Internet, Routing, VPN Troubleshooting on
>>>> http://www.ChicagoTech.net
>>>> How to Setup Windows, Network, VPN & Remote Access on
>>>> http://www.HowToNetworking.com
>>>> "PGPhantom" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>> I have a bit of a connundrum in configuration that I am unable to
>>>> resolve
>>>> and would appreciate any help. On a new Windows 2003 server which is
>>>> a
>>>> stand alone server in an existing AD domain we have 2 NICS installed.
>>>> The
>>>> settings are as follows:
>>>> OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
>>>> INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway 192.168.87.1
>>>>
>>>> They are configured that way because we have people accessing the
>>>> server
>>>> remotely to set up software so the outside NIC is connected to a
>>>> router and
>>>> then a cable modem. The inside joins it to the domain where users are
>>>> accessing the server. We have a remote site that has VPN set up to
>>>> the
>>>> site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the
>>>> remote
>>>> site cannot ping the 192.168.87.153 IP - It times out. If I disable
>>>> the
>>>> outside they can ping it without issue. I have changed the
>>>> configuration
>>>> around, removing gateways, settng the INSIDE as primary etc but to no
>>>> effect. As it currently stands, If I disable the OUTSIDE, everything
>>>> works
>>>> but the software developers cannot RDP in. If I enable it, the
>>>> developers
>>>> can come in, local users can connect without issue but the remote site
>>>> cannot?
>>>>
>>>> I assume that I might have to add a static route somewhere but just
>>>> cannot
>>>> get the right configuration? If anyone has any expertise in this area
>>>> I
>>>> would greatly appreciate the help.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Making changes to an LMHOSTS file won't have any effect on a login to AD.
An AD client finds the login server through the SRV records in DNS.

You say thet the "main" AD server is at 192.168.87.50 . Is the
multihomed server a DC?

"PGPhantom" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> To add to this - I even added the 192.168.87.50 into the LMHOSTS file
> hoping that would solve it and on the both INSIDE and OUTSIDE I have
> 192.168.87.50 as the primary and only DNS server as the 192.168.87.50 is
> the DNS server for the domain.
>
> "PGPhantom" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> This one keeps confounding me - I though I had the issue licked as
>> everything appeared to be working BUT ... When on the server now, people
>> using a domain log on have an issue as it cannot get authenticated? It
>> gives an RPC server unavailable error. The main AD server for the domain
>> is on 192.168.87.50. Do I have to add a route for that too? If so,
>> what?
>>
>> "Bill Grant" <not.available@online> wrote in message
>> news:(E-Mail Removed)...
>>> That is pretty much what you have to do. The default route must be
>>> out to the Internet. To route a particular set of addresses to some
>>> other gateway you need to use static routing.
>>>
>>> In the route command you need to specify the subnet, the subnet mask
>>> and the IP address of the router which is the next hop towards the
>>> target. The machine can decide which interface to use (because it has to
>>> be in the same subnet as the next hop router).
>>>
>>> To send all traffic for the subnet 10.0.1.0/24 to a router at
>>> 192.168.87.1 the command would be
>>>
>>> route add 10.0.1.0 255.255.255.0 192.168.87.1
>>>
>>> With that route in place, any traffic for an address beginning with
>>> 10.0.1 would be directed to the router at 192.168.87.1 through interface
>>> 192.168.87.153 (ie the inside NIC).
>>>
>>> Remember to add the -p option to the command so that it survives a
>>> reboot.
>>>
>>>
>>> "PGPhantom" <(E-Mail Removed)> wrote in message
>>> news:%23qo%(E-Mail Removed)...
>>>> The OUTSIDE Nic is the Internet. The inside is the local network which
>>>> connects via another gateway to a remote site that is on a 10.0.1.x
>>>> subnet. Should I: Delete the default gateway on INSIDE and then "route
>>>> add 10.0.1.1 mask255.255.255.0 192.168.87.1" on the server?
>>>>
>>>> What is the right syntax for the route add as I am connecting to the
>>>> 192.168.87.x network INTERNAL then via the 192.168.87.1 gateway to the
>>>> remote site which is on gateway 10.0.1.1?
>>>>
>>>> "Bill Grant" <not.available@online> wrote in message
>>>> news:%(E-Mail Removed)...
>>>>> You cannot have different gateway settings on the NICs. The only
>>>>> default gateway setting should be on the outside NIC pointing to the
>>>>> router. The gateway setting on the inside NIC should be blank.
>>>>>
>>>>> "Robert L [MVP - Networking]" <(E-Mail Removed)> wrote in message
>>>>> news:O7%23%(E-Mail Removed)...
>>>>> We need more details to help. Since you setup two gateways, can we
>>>>> assuming you have two internet access? Or what do 192.168.1.1 and
>>>>> 192.168.87.1 connect to ?
>>>>>
>>>>> Bob Lin, MS-MVP, MCSE & CNE
>>>>> Networking, Internet, Routing, VPN Troubleshooting on
>>>>> http://www.ChicagoTech.net
>>>>> How to Setup Windows, Network, VPN & Remote Access on
>>>>> http://www.HowToNetworking.com
>>>>> "PGPhantom" <(E-Mail Removed)> wrote in message
>>>>> news:(E-Mail Removed)...
>>>>> I have a bit of a connundrum in configuration that I am unable to
>>>>> resolve
>>>>> and would appreciate any help. On a new Windows 2003 server which
>>>>> is a
>>>>> stand alone server in an existing AD domain we have 2 NICS installed.
>>>>> The
>>>>> settings are as follows:
>>>>> OUTSIDE: IP 192.168.1.2, Subnet 255.255.255.0, Gateway 192.168.1.1.
>>>>> INSIDE: IP 192.168.87.153, Subnet 255.255.255.0, Gateway
>>>>> 192.168.87.1
>>>>>
>>>>> They are configured that way because we have people accessing the
>>>>> server
>>>>> remotely to set up software so the outside NIC is connected to a
>>>>> router and
>>>>> then a cable modem. The inside joins it to the domain where users
>>>>> are
>>>>> accessing the server. We have a remote site that has VPN set up to
>>>>> the
>>>>> site on the 192.168.87.x subnet. When the OUTSIDE is enabled, the
>>>>> remote
>>>>> site cannot ping the 192.168.87.153 IP - It times out. If I disable
>>>>> the
>>>>> outside they can ping it without issue. I have changed the
>>>>> configuration
>>>>> around, removing gateways, settng the INSIDE as primary etc but to no
>>>>> effect. As it currently stands, If I disable the OUTSIDE, everything
>>>>> works
>>>>> but the software developers cannot RDP in. If I enable it, the
>>>>> developers
>>>>> can come in, local users can connect without issue but the remote
>>>>> site
>>>>> cannot?
>>>>>
>>>>> I assume that I might have to add a static route somewhere but just
>>>>> cannot
>>>>> get the right configuration? If anyone has any expertise in this
>>>>> area I
>>>>> would greatly appreciate the help.
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>