Re^3: Debugging LWP

I am running this script from a hosted Windows server. So I cannot run a telnet. But, what I just did was bring the script to my local machine which has IIS and ActivePerl installed. Install the SSLeay and tested the script locally. It ran just fine which tells me it's the hosters server which is causing the problem. I am going to call them now. Hopefully, they can get to the bottom of this, else I will have to switch servers.

Comment on Re^3: Debugging LWP

Replies are listed 'Best First'.
Re^4: Debugging LWP by renodino (Curate) on Feb 12, 2006 at 00:45 UTC
(Longshot guess, but I've been burned by this in the past too) Have you tried connecting via a numeric IP address ? Windows has been known to have some nasty resolver caching behaviors which, if not registry hacked properly, can cause it to hang onto a bad DNS resolution for a long time...so if your target has changed its IP address recently, the Windows resolver cache may not have flushed yet. Here's the story wrt WinXP...	[reply]

Replies are listed 'Best First'.

Re^4: Debugging LWP
by renodino (Curate) on Feb 12, 2006 at 00:45 UTC

Have you tried connecting via a numeric IP address ? Windows has been known to have some nasty resolver caching behaviors which, if not registry hacked properly, can cause it to hang onto a bad DNS resolution for a long time...so if your target has changed its IP address recently, the Windows resolver cache may not have flushed yet.

Here's the story wrt WinXP...

[reply]