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@newsgroup> wrote in message
newsABCF76E-4AA8-4B4B-A945-4C3CA1A37122@newsgroup

>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
>

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
http://support.microsoft.com for regional support phone numbers.

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@newsgroup> wrote in message
newsABCF76E-4AA8-4B4B-A945-4C3CA1A37122@newsgroup

>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@newsgroup> wrote in message
news:6D57A89C-E6C9-462C-8342-0C498252D800@newsgroup

> 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

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

Ace