Wininet.dll Error 12007 - Name not resolved

[William Buntain]

I have an application that distributes updates over the Internet using
wininet.dll. I have a user that is reporting that they are getting an
"Error! 12007 - Name not resolved" when they try to use this function.
They are behind a firewall. Is that the source of the problem? Is
there a workaround?

=============================================
William E. Buntain
C&C Software
ca...@ticnet.com

[Jim Millar]

Hope this helps.
You should post more information...

Event ID
12007

Event Message
The server name or address could not be resolved. This message might
indicate an error in client or server configuration settings for DNS, WINS,
or DHCP services that are actively in use. Review the TCP/IP properties for
these services

"William Buntain" <ca...@ticnet.com> wrote in message
news:7AE69E7CE08666C9.A37CC61A...@lp.airnews.net...

[William Buntain]

I appreciate the response. I was aware of the meaning of the error
message but not sure how the customer's use of a proxy server might be a
factor, since I have been able to run the FTP session on test machines
without problems. I'm not exactly sure what the comment means, "You
should post more information." What information would be useful?

--

[William Buntain]

I appreciate the response. After I posted it I realized that I made a
mistake. The issue is the customer's use of a proxy server, not a
firewall. I cancelled it and resent it with the correct info, but
apparently you got the original message.

I was aware of the meaning of the error message but not sure how the
customer's use of a proxy server might be a factor, since I have been

able to run the FTP session on test machines without problems. As to
your comment that "You should post more information," what information
would be useful?

--

[Jim Millar]

William,

Proxy is most definitely a factor.

Perhaps your are not aware, (as I wasn't until it bit me in the ass)
FTP works on sockets (you knew that)
A normal workstation behind a firewall will be set up for internet access by
pointing
Internet Explorer to the proxy server.
Works great, EXCEPT, this does nothing for sockets.

To get any sockets based app to run behind proxy the workstation
MUST load proxy client.

I think you'll find that if your users load proxy client your app will run
fine.
NOTE:
Proxy client setup MUST be run from the share on the server.
Usually : \\<ProxyServer>\mspclnt\setup.exe

More Helpful?

Jim

"William Buntain" <ca...@ticnet.com> wrote in message

news:E561632C00768289.1E450B56...@lp.airnews.net...

[William Buntain]

Thanks a lot. I'll check it out.