Huh. It does have it. But why didn’t 127.0.0.1 work, I wonder?
From: stunnel-users [mailto:[email protected]] On Behalf Of Carter Browne Sent: Thursday, January 18, 2018 2:11 PM To: [email protected] Subject: Re: [stunnel-users] Re (2): Problems with stunnel and cox.net on Windows 7
You should check your hosts file in \windows\system32\drivers\etc.
Make sure it has an entry:
127.0.0.1 localhost
The text claims it doesn't need it, but it doesn't hurt to have it, and I'm not sure I totally believe the text.
Carter
On 1/18/2018 1:55 PM, Phil Smith III wrote:
Oh, the logging works--it just doesn't like it there in the file. I have it earlier and it's fine. --------------
C:\Users\phsiii>ls -ld \temp\stunnel-log.txt -rw-r--r-- 1 phsiii None 266835 Jan 18 08:52 \temp\stunnel-log.txt
# That's Cygwin ls -- remember, this is Windows 7
C:\Users\phsiii>nslookup localhost Server: UnKnown Address: 2001:4860:4860::8888
*** UnKnown can't find localhost: No response from server
# Windows nslookup (per "which nslookup") -------------- Odd. -----Original Message----- From: stunnel-users [mailto:[email protected]] On Behalf Of [email protected] mailto:[email protected] Sent: Thursday, January 18, 2018 1:13 PM To: [email protected] mailto:[email protected] Subject: [stunnel-users] Re (2): Problems with stunnel and cox.net on Windows 7
From: "Phil Smith III" mailto:[email protected] [email protected] Date: Thu, 18 Jan 2018 12:47:47 -0500
while the output= wasn't accepted (it said it wasn't valid there),
Does the file exist? If not, can stunnel create it? Can you read it with an editor. Can you write into it interactively?
What does "ls -ld C:\temp\stunnel-log.txt" or Win equivalent give?
changing 127.0.0.1 to localhost seems to have fixed it!
What does "nslookup localhost" report?
Regards, ... P.
-
Phil Smith III