RE: Follow-up, Re: Can anybody make any sense out of this? (it involves lack of DNS)

["Porterfield, Sean" <SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx>]

> From: James Lampert

> All I know about the aforementioned "proxy voodoo" is that it involves
> a host table entry that maps the desired domain into an IP address in
> one of the "local" blocks. I'm guessing that's the proxy's IP address.
> But I haven't a clue what the proxy port would be.

Based on that description, it sounds to me like they're running a transparent proxy that may not be on the gateway device.  If they don't tell browsers or other software about the proxy yet it works, that's my only explanation.  If that's the case, I would expect the proxy ports to be 80 for http and 443 for https.

I can't say I've actually heard of anyone doing such a thing, though.  I would also think if they do the same for other clients, then the DNS server would return the proxy IP for everything.  Really, the whole thing doesn't make sense.
--
Sean Porterfield

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged.  If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited.  Thank you.
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------