Help proxy binds to wrong NIC

I have one Windows 2008 Standard Server with two NICS:
NIC1: LAN 192.168.200.1
NIC2: WAN 10.200.200.2

DNS, DHCP, AD, Network Policy & Access Services are installed. All seems to
be working fine.
PPTP VPN works fine through NIC2.

Then I installed the Squid Caching Proxy and it seems to bind to NIC2. So on
the LAN clients I have to point the proxy to 10:200:200:2:3128 to get it to
work. So I tried another proxy called "FreeProxy", again it binds to NIC2.
Other than that it all seems to work.

Have I done something wrong in the server setup, shouldn't the LAN clients
point to 192.168.200.1:3128. Will I start to have problems?

Any help would be appreciated. Thanking you in advance.

Regards
Gitendra

 

"Gitendra" <c2gaustralia@hotmail.com> wrote in message
newsABCF76E-4AA8-4B4B-A945-4C3CA1A37122@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>I have one Windows 2008 Standard Server with two NICS:
> NIC1: LAN 192.168.200.1
> NIC2: WAN 10.200.200.2
>
> DNS, DHCP, AD, Network Policy & Access Services are installed. All seems
> to be working fine.
> PPTP VPN works fine through NIC2.
>
> Then I installed the Squid Caching Proxy and it seems to bind to NIC2. So
> on the LAN clients I have to point the proxy to 10:200:200:2:3128 to get
> it to work. So I tried another proxy called "FreeProxy", again it binds to
> NIC2. Other than that it all seems to work.
>
> Have I done something wrong in the server setup, shouldn't the LAN clients
> point to 192.168.200.1:3128. Will I start to have problems?
>
> Any help would be appreciated. Thanking you in advance.
>
> Regards
> Gitendra
><!--colorc--><!--/colorc-->


Go into Network Connections windows, Advanced Menu, Advanced Settings,
change the binding order so the internal NIC is the first in the list.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
for regional support phone numbers.

 

First thing I tried; LAN is definitely first (top) on the list, followed by
the WAN then “Remote Access Connections”. When that didn’t work I even went
to the extent of re-loading the Server with the network cables swapped
around so the original LAN NIC became the WAN NIC & vice versa.

I’m pretty sure the binding is set right, as when running the DHCP wizard
the LAN IP address is on the top of the list. If I swap the bindings it
changes around.

I appreciate the help; at least I know I was heading in the right direction.
It’s got me frustrated. Any other ideas please?
Thanks
Gitendra

"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:OSD21e2GKHA.3948@TK2MSFTNGP03.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "Gitendra" <c2gaustralia@hotmail.com> wrote in message
> newsABCF76E-4AA8-4B4B-A945-4C3CA1A37122@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
>>I have one Windows 2008 Standard Server with two NICS:
>> NIC1: LAN 192.168.200.1
>> NIC2: WAN 10.200.200.2
>>
>> DNS, DHCP, AD, Network Policy & Access Services are installed. All seems
>> to be working fine.
>> PPTP VPN works fine through NIC2.
>>
>> Then I installed the Squid Caching Proxy and it seems to bind to NIC2. So
>> on the LAN clients I have to point the proxy to 10:200:200:2:3128 to get
>> it to work. So I tried another proxy called "FreeProxy", again it binds
>> to NIC2. Other than that it all seems to work.
>>
>> Have I done something wrong in the server setup, shouldn't the LAN
>> clients point to 192.168.200.1:3128. Will I start to have problems?
>>
>> Any help would be appreciated. Thanking you in advance.
>>
>> Regards
>> Gitendra
>><!--colorc--><!--/colorc-->
>
>
> Go into Network Connections windows, Advanced Menu, Advanced Settings,
> change the binding order so the internal NIC is the first in the list.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum to benefit from collaboration
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> for regional support phone numbers. <!--colorc--><!--/colorc-->

 

"Gitendra" <c2gaustralia@hotmail.com> wrote in message
news:1CC6957B-FBAB-44B8-9481-78CB67832CF1@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> First thing I tried; LAN is definitely first (top) on the list, followed
> by the WAN then “Remote Access Connections”. When that didn’t work I even
> went to the extent of re-loading the Server with the network cables
> swapped around so the original LAN NIC became the WAN NIC & vice versa.
>
> I’m pretty sure the binding is set right, as when running the DHCP wizard
> the LAN IP address is on the top of the list. If I swap the bindings it
> changes around.
>
> I appreciate the help; at least I know I was heading in the right
> direction. It’s got me frustrated. Any other ideas please?
> Thanks
> Gitendra
><!--colorc--><!--/colorc-->

Well, the LAN interface MUST be at the top. Either way, I would at least
recommend to set it that way. This is because the LAN interface needs to be
the default for communications for the internal network.

As for the proxy, after you changed the binding order, restarted the
machine, have you tried to reinstall the proxy, or reset the interface in
its properties?

Ace

 

"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:#oojK66GKHA.4552@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "Gitendra" <c2gaustralia@hotmail.com> wrote in message
> news:1CC6957B-FBAB-44B8-9481-78CB67832CF1@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
>> First thing I tried; LAN is definitely first (top) on the list, followed
>> by the WAN then “Remote Access Connections”. When that didn’t work I even
>> went to the extent of re-loading the Server with the network cables
>> swapped around so the original LAN NIC became the WAN NIC & vice versa.
>>
>> I’m pretty sure the binding is set right, as when running the DHCP wizard
>> the LAN IP address is on the top of the list. If I swap the bindings it
>> changes around.
>>
>> I appreciate the help; at least I know I was heading in the right
>> direction. It’s got me frustrated. Any other ideas please?
>> Thanks
>> Gitendra
>><!--colorc--><!--/colorc-->
>
> Well, the LAN interface MUST be at the top. Either way, I would at least
> recommend to set it that way. This is because the LAN interface needs to
> be the default for communications for the internal network.
>
> As for the proxy, after you changed the binding order, restarted the
> machine, have you tried to reinstall the proxy, or reset the interface in
> its properties?
>
> Ace
>
><!--colorc--><!--/colorc-->

The first question has to be this - why are you running remote access and
proxy servers on your DC/DNS server? That is asking for trouble.

 

"Bill Grant" <not.available@online> wrote in message
news:eJvFlM7GKHA.4760@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> The first question has to be this - why are you running remote access
> and proxy servers on your DC/DNS server? That is asking for trouble.<!--colorc--><!--/colorc-->

I was going to address that, but now that you have, it's a very good
question. You know how I feel about multihomed DCs.

Gitendra, what Bill's saying, is a DC with more than one NIC, IP and/or
RRAS, is called a multihomed DC. This type of config is not recommended
anyway because it causes problems with AD. Unless of course, this is SBS,
but then again, you would have installed the available ISA feature.

Here's a comprehensive explanation:

Multihomed DCs with DNS, RRAS, and/or PPPoE adapters


Ace

 

Bill, I put two NICs so I can isolate the LAN side:
The WAN side connects directly into a DSL router. The router has DHCP
enabled (10.200.200.50 to 10.200.200.254). The DSL router also has two VOIP
devices connected to it that handles the phone calls in the office.

I didn’t want to touch the DSL router or the VOIP settings. The only change
I made in the router was to forward the VPN port (1723) to the server WAN
NIC. (10.200.200.2)

So the reasoning goes: if the VOIP fails, it’s the phone company’s problem.

Ace, I am pointing all internal clients to the server which is running DNS;
of course any DNS it can’t resolve is then sent to the router, and from
there to the ISP, there is only one server. Thanks for the link, most of it
made sense. I'm learning.

I also re-installed the whole server and proxy from scratch with the LAN NIC
at the top, no luck.
It was the 64bit version of Server 2008 I ran initially; now I have loaded
the 32bit version, no luck.

Bill, the proxy is there basically to speed up some graphics heavy web pages
that rarely change; also our download quota is small ,so it will also help
with Windows/Program updates. I understand it’s best to put the proxy on a
different machine, but its either this or no proxy at all.

I will plod on, any suggestions will be appreciated.

Thanks again,
Gitendra


"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:%23oojK66GKHA.4552@TK2MSFTNGP05.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "Gitendra" <c2gaustralia@hotmail.com> wrote in message
> news:1CC6957B-FBAB-44B8-9481-78CB67832CF1@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
>> First thing I tried; LAN is definitely first (top) on the list, followed
>> by the WAN then “Remote Access Connections”. When that didn’t work I even
>> went to the extent of re-loading the Server with the network cables
>> swapped around so the original LAN NIC became the WAN NIC & vice versa.
>>
>> I’m pretty sure the binding is set right, as when running the DHCP wizard
>> the LAN IP address is on the top of the list. If I swap the bindings it
>> changes around.
>>
>> I appreciate the help; at least I know I was heading in the right
>> direction. It’s got me frustrated. Any other ideas please?
>> Thanks
>> Gitendra
>><!--colorc--><!--/colorc-->
>
> Well, the LAN interface MUST be at the top. Either way, I would at least
> recommend to set it that way. This is because the LAN interface needs to
> be the default for communications for the internal network.
>
> As for the proxy, after you changed the binding order, restarted the
> machine, have you tried to reinstall the proxy, or reset the interface in
> its properties?
>
> Ace
>
> <!--colorc--><!--/colorc-->

 

"Gitendra" <c2gaustralia@hotmail.com> wrote in message
news:BC4BAF25-8B55-46C5-A286-405E9B9CDF90@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Bill, I put two NICs so I can isolate the LAN side:
> The WAN side connects directly into a DSL router. The router has DHCP
> enabled (10.200.200.50 to 10.200.200.254). The DSL router also has two
> VOIP devices connected to it that handles the phone calls in the office.
>
> I didn’t want to touch the DSL router or the VOIP settings. The only
> change I made in the router was to forward the VPN port (1723) to the
> server WAN NIC. (10.200.200.2)
>
> So the reasoning goes: if the VOIP fails, it’s the phone company’s
> problem.
>
> Ace, I am pointing all internal clients to the server which is running
> DNS; of course any DNS it can’t resolve is then sent to the router, and
> from there to the ISP, there is only one server. Thanks for the link, most
> of it made sense. I'm learning.
>
> I also re-installed the whole server and proxy from scratch with the LAN
> NIC at the top, no luck.
> It was the 64bit version of Server 2008 I ran initially; now I have loaded
> the 32bit version, no luck.
>
> Bill, the proxy is there basically to speed up some graphics heavy web
> pages that rarely change; also our download quota is small ,so it will
> also help with Windows/Program updates. I understand it’s best to put the
> proxy on a different machine, but its either this or no proxy at all.
>
> I will plod on, any suggestions will be appreciated.
>
> Thanks again,
> Gitendra
><!--colorc--><!--/colorc-->

Keep in mind, with multihoming a DC, the DC will register the extra NIC and
RRAS interface IP addresses into DNS. If a client queries for the domain
resources, and gets one of the other IP addresses, it will not be able to
find the DC.

Ace

 

Okay, I loaded up a Windows 2003 Standard Server. Nothing fancy, just ran
the "Configure the Server Wizard ", it setup DNS, DHCP, RRAS. I then setup
Squid 3.0 with the exact settings as on Server 2008.

Everything worked perfectly on the 2003 server. Squid bound to the internal
LAN (top of list) without a problem.
Seems to be problem with Server 2008 or something I'm not doing. Whatever it
is I've tried Squid, FreeProxy and Paw Proxy, they all bind to the WAN NIC
(Second on list).

At least I know its related to Server 2008 now!

Anyone had the same problem, please let me know.

Gitendra

"Gitendra" <c2gaustralia@hotmail.com> wrote in message
newsABCF76E-4AA8-4B4B-A945-4C3CA1A37122@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>I have one Windows 2008 Standard Server with two NICS:
> NIC1: LAN 192.168.200.1
> NIC2: WAN 10.200.200.2
>
> DNS, DHCP, AD, Network Policy & Access Services are installed. All seems
> to be working fine.
> PPTP VPN works fine through NIC2.
>
> Then I installed the Squid Caching Proxy and it seems to bind to NIC2. So
> on the LAN clients I have to point the proxy to 10:200:200:2:3128 to get
> it to work. So I tried another proxy called "FreeProxy", again it binds to
> NIC2. Other than that it all seems to work.
>
> Have I done something wrong in the server setup, shouldn't the LAN clients
> point to 192.168.200.1:3128. Will I start to have problems?
>
> Any help would be appreciated. Thanking you in advance.
>
> Regards
> Gitendra
> <!--colorc--><!--/colorc-->

 

"Gitendra" <c2gaustralia@hotmail.com> wrote in message
news:6D57A89C-E6C9-462C-8342-0C498252D800@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Okay, I loaded up a Windows 2003 Standard Server. Nothing fancy, just ran
> the "Configure the Server Wizard ", it setup DNS, DHCP, RRAS. I then setup
> Squid 3.0 with the exact settings as on Server 2008.
>
> Everything worked perfectly on the 2003 server. Squid bound to the
> internal LAN (top of list) without a problem.
> Seems to be problem with Server 2008 or something I'm not doing. Whatever
> it is I've tried Squid, FreeProxy and Paw Proxy, they all bind to the WAN
> NIC (Second on list).
>
> At least I know its related to Server 2008 now!
>
> Anyone had the same problem, please let me know.
>
> Gitendra<!--colorc--><!--/colorc-->


Interesting. Now curious, what SP level is your 2008?

Ace