Discussion Locked

Proxy Server confusion

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

To anyone who can help:

hi,
I am currently installing a new NT box running MS Proxy Server 2.0 and Exchange 5.5 (as per the SMALL BUSINESS SERVER 4.5 package). I am in the process of configuring the various Proxy servers but i am confused as regards the LAT. My confusion comes from various articles/books which would appear to contradict each other. Some sources say that external NIC's should have the fixed IP address (as given by my ISP) entered into the LAT while other sources say this must not be done as this would constitute a security breach by opening a traceable route to the internal network. I am including the relevant excerpts from some of the sources below....could someone please enlighten me as to the correct procedure (i.e. Best Practice) and explain why? thanks for any + all help.
Pete.
any and all responses can also be sent to pp@citac.net

excerpt below taken from the book "IIS 4 and Proxy Server 2 24seven"

"Note that the dialog box shows any existing RAS connection of your NT server as a valid network interface, even though it will be grayed out near the bottom of the dialog box. If you have a static IP for your network connection to an ISP, that IP address should be part of the LAT."

and

"[TheLAT] should include the IP address of any NIC installed in the NT Server, even NICs that are connected directly to the Internet. Contacting all addresses entered here will be handled by the internal WinSockets of each workstation and will not be forwarded to the Web Proxy or WinSock Proxy Servers for outside remoting."

Article published on the Techrepublic site Jan 4, 2001 by Troy Thompson:

"Ensure that external addresses are not entered in internal IP ranges. This would identify them as internal addresses, which is a security breach and could allow intruders to access your internal network."

6 replies

by jdbailey

Try reading some Cisco references for networking.

Any network setup should consider security. I'm a little rusty on some of these topics. You may want to check anything I say at http://www.cisco.com/univercd/home/home.htm or just read http://www.cisco.com/univercd/cc/td/doc/product/iaabu/centri4/user/scf4ch3.htm for a better understanding.

A proxy server provides a focal-point, choke-funnel, check-stop, whatever for your network to control internet access of your intranet, just a proxy isnot considered securing a network.

Most networks these days are IP wasteful. If your network is behind a firewall, then why not use public IP addresses like the class-A 10.0.0.0 on your intranet. Public IP addresses are not routable across a router or even outside the local LAN. Anyway to little space to much to say.

Read up on the subject: Access Control List (topic can be found on Cisco site). This should help you understand why some addresses are hidden inside your network, while others are required to complete an internet connection.

I hope the links above will help -- Jim

by sbworks

I have two client sites on SBS 4.5 and I found that the stock setup wizard is doing thing correctly and that the IIS 4 / PS2 24-7 is a useless piece of crap. Worst book I ever bought. The web hosting IIS half of the book is reasonably good but the proxy server section is rediculously bad.

I think the wizard sets up the IP addresses in the LAT, and I recommend leaving it there. Technet might have something on it if your feeling really patient.....

by jodyc

SBS out of the box comes with a Proxy Config that is suitable (and secure) for most situations. Why do you want to mess with it?

P.S. I wouldn't put the address in the NAT.

by rrussell110

I am running the same setup and I do not use the IP from the external nic in my LAT. The only range I used was from internal network. This will be very helpful if you decide to enable packet filtering which requires an external interface, (or connected to the internet.)

by anthonybernardino

Make sure you internal lan is RFC1918 compatible. That's an address in 192.168.x.x. range or 10.x.x.x. range. Those addresses are non-routable. Then when you configure LAT, use those addresses initially, and the external NIC address needs to be up not as a scope, but as 1 address. For example: 220.78.90.6 is your external IP address. Then you set it up as from 220.78.90.6 to 220.78.90.6. That way your LAT would look like:

10.x.x.x. to 10.x.x.x.
192.168.x.x. to 192.168.x.x.
220.78.90.6 to 220.78.90.6

Also on the internal LAN NIC you'll need to put the gateway address as 220.78.90.6 (as per example)

I would try it both ways. 1 with the external NIC address in the LAT, and another without it. Then you can see what works for you.

Make sure you have RIP installed as well.

by aoreilly

In their knodledgebase article Q186918, Microsoft says: "Build the Local Address Table (LAT) so that it uses the IP range of the internal NIC.

NOTE: Only include the internal IP addresses in the LAT. This should also include the internal IP address on the Proxy Server. Proxy Server uses the LAT to determine which requests to answer. In addition, Proxy Server uses the LAT to determine which interface to use when sending requests out to the external network. If all IP addresses on the Proxy Server are included in the LAT, Proxy Server will only be useful as a caching server. If none of the IP addresses on the Proxy Server are included in the LAT, no requests will be answered by the Proxy Server." Hope this helps - Aidan

This discussion is closed to new replies.