I didn't change the LAT table! What I wound up doing is putting
the external interface on a separate private subnet than the internal
interface and I still got the same problem. Turns out it probably was
the LAT because it encompassed the whole 192.168 C Class. I thought it
was only doing 192.168.1.1-255 not 192.168.1.1-.255.255. Anyway, I wound
up changing the external interface to have its original ip which was a
public ip and i didn't get any errors starting the services but nobody
got get web pages. Users were able to connect with AIM, and any other
app that connects externally using ports other than 80. After
re-applying SP1, and then removing Proxy and re-installing and
re-applying SP1, users still could not connect to web pages. After
checking some more settings, I relized the default website was stopped,
I started it and users were able to surf again. Didn't know that the web
site had to be running to have the proxy filter up. 
         
        Anyway, would having an address on the external interface with
an private ip that was in the LAT table have cause the services to not
start?

                -----Original Message----- 
                From: Chris Bodnar 
                Sent: Thu 8/30/2001 3:06 PM 
                To: NT System Admin Issues 
                Cc: 
                Subject: RE: Proxy Issues
                
                

                Did you modify the LAT table when you made the change?
If you gave the
                external interface an IP address from the internal
range, you will need to
                exclude it from the LAT.
                
                
                
                Chris Bodnar
                The Lehigh Group
                610-966-9702 X:134
                
                -----Original Message-----
                From: Paul Armstrong [mailto:[EMAIL PROTECTED]]
                Sent: Thursday, August 30, 2001 2:28 PM
                To: NT System Admin Issues
                Subject: Proxy Issues
                
                Hello All,
                
                I am having an issue with Proxy 2.0 where clients are
unable to brows
                web pages but can connect to other external resources.
The problem
                started when I changed the IP address of the external
interface so that
                I can implement this device we have to aggreate &
load-balace two wan
                connections. I changed the public interface from a
public ip to a
                private ip on the same subnet as the internal interface.
I kept getting
                errors that prevent ed the services from started, so
then I changed the
                external ip to another private ip but on a different
subnet as the
                internal interface. Still same problem. So I restored
the external NIC
                to have its public ip as before. I am able to surf from
the server and
                clients are able to connect to other external resources
other than web
                pages. I have no clue as to why they cannot browse web
pages but can
                access other resouces such as AIM, etc. Any clue as to
why this is
                happening? The server is NT 4 SP6 running Proxy 2.0 SP1.
ANy help would
                be greatly appreciated!
                
                
        
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
                
        
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
                
                

m����,�vޖ�(~���(����+vh��+-r����

Reply via email to