We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

DNS returns WSANO_DATA. Reason ?

pangofil
pangofil asked
on
Medium Priority
1,675 Views
Last Modified: 2013-12-23
Hi.
Does somebody know what can be reason for follow :
gethosbyname() sometime returns WSANO_DATA, after I've used
Auto Connect feature in Win95.
If I start my program when PC is already connected
via DialUp - everything is OK.
TIA.

Comment
Watch Question

Commented:
Are you using the Win95 Winsock?

When using any winsock, the first call is always to WSAStartup. This fills a structure with information about the winsock you are using, so that TCP/IP programs can be made aware of any limitations that exist with your winsock. The WSANO_DATA response comes when the winsock app looks to the WSAData structure, and finds that it has not been filled in completely.

It sounds like you program is starting before WSAStartup completes when you use autoconnect. Watch carefully and see if you can tell whether your program is starting before you see the login complete.

You might also check to make sure that when you right click the  internet icon, the information on the connection tab is correct.

Harry

Author

Commented:
Yes I'm using Win95 winsock.
And I call WSAStartup() before any network action.
And something else :
  I'm writing 16-bit program so i call 32-bit exe file,
  which performs some WinSock actions ( gethostbyname() )
  for autoconnecting (16-bit Winsock can't perform autoconnect).
  After host resolved the 32-bit app PostMessage about connecting
  result. After what 16-bit app continues ( tries to resolve host   etc ... ). And here ( after WSAStartup has completed )
  some time I get the problem, described above.

Commented:
ask in the programming section

Author

Commented:
Thanks for responses - I found out that's a problem.
That was becasuse I mixed 16-bit & 32-bit.
Must load 16-bit Winsock after AutoConnection has been completed.

Commented:
Sounds to me like I told you exactly where to look, doesn't it?

And the reason you rejected my answer is...?

Author

Commented:
To hpierson :
May be You're right.
I just didn't understand your answer ( it didn't help me to solve  the problem ).
Just answer again - I'll accept it.

PS : Sorry for nasty English - I'm working on it
Commented:
Pangofil,

I hope I didn't come across the wrong way,...it seems from your solution that you realized that the problem was in the general area I described.

By the way, I have no problem with your English.


Best Regards,

Harry

Are you using the Win95 Winsock?

When using any winsock, the first call is always to WSAStartup. This fills a structure with information about the winsock you are using, so that TCP/IP programs can be made aware of any limitations that exist with your winsock. The WSANO_DATA response comes when the winsock app looks to the WSAData structure, and finds that it has not been filled in completely.

It sounds like you program is starting before WSAStartup completes when you use autoconnect. Watch carefully and see if you can tell whether your program is starting before you see the login complete.

You might also check to make sure that when you right click the internet icon, the information on the connection tab is correct.

Harry

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.