Re: Always takes 100s to establish connection...why!?
From: Mike Blake-Knox (mikebkdont_at_spamintrex.net)
Date: 05/15/04
- Next message: Jman: "Re: How to use axWebBrowser component with Proxy server"
- Previous message: Andrew S \(Infragistics\): "Re: Restricted Control Height"
- In reply to: TJ: "Re: Always takes 100s to establish connection...why!?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 15 May 2004 11:29:21 EDT
In article <7207F4BD-254A-42B8-8664-50BBC3CD9A3F@microsoft.com>, Tj wrote:
> However, when I tried to connect to the server by IP, not DNS (something like ftp.connect("123.123.123.123")), it still has
same problem.
My problem wasn't using (or not using) DNS in connecting to the FTP server. The problem was that the FTP server wanted to put
a hostname (as well as the source IP address) into its log file. When it tried to do a reverse DNS lookup to find the
hostname corresponding to the source IP address, the local DNS server couldn't find the address, then forwarded the request
upstream where it timed out.
If this is the cause of your problem, there are several things you might do. These include deciding to just live with it,
configuring the FTP server to not do the reverse DNS lookup, putting your IP address in its host file or ensuring that the
source host's IP address has a DNS entry.
Hope this helps.
Mike Blake-Knox
- Next message: Jman: "Re: How to use axWebBrowser component with Proxy server"
- Previous message: Andrew S \(Infragistics\): "Re: Restricted Control Height"
- In reply to: TJ: "Re: Always takes 100s to establish connection...why!?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
