Msproxy LAT

• To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
• Subject: Msproxy LAT
• From: Colin McNab <colinDIGITAL-ANIMATIONS.COM>
• Date: Thu, 27 Aug 1998 14:51:15 +0100
• Reply-To: Colin McNab <colinDIGITAL-ANIMATIONS.COM>
• Sender: Windows NT BugTraq Mailing List <NTBUGTRAQLISTSERV.NTBUGTRAQ.COM>

Hi,
I am basically a lurker on this mailing list and most of it goes clean
over my head...
But at the risk of stating what may be an obvious set of circumstances
to you guys who know where you're at, I have to tell someone about a
recent "discovery" I made.
When looking at the MSPLAT on NT I noticed some addresses which I new
were definitely not part of our internal network. Out of curiosity I
attempted a traceroute and discovered the name of a local company.
In a fit of total paranoia I started an investigation as to how this
address could be listed as a local address.
Eventually I discovered that when the proxy had been reconfigured the
LAT was generated from all network cards whilst a connection existed on
the outside network to this IP (I think this is may be the default). It
all seems pretty obvious now I know what's going on and was easily fixed
by editing the LAT, but I wonder how many others are persuaded by the
seaming simplicity of NT's GUI set up for IP stuff without knowing how
it all works and leaving gaping holes.

• Prev by Date: Re: MS Security Bulletin MS98-012, security updates for Microsoft PPT P
• Next by Date: "NERP" DoS attack possible in Oracle
• Prev by thread: Administrivia #17800
• Next by thread: Re: Msproxy LAT
• Index(es):
  • Date
  • Thread