0.0.0.[real last ip number] LocalIP Return from Winsock Control

[lili96ilil]

I'm developing an application for a for my company that communicates from app to app over our intranet. I installed the program and it seems to run find on all of the Win2k machines. All of the WinNT 4.0 machines I installed the app on fail to report their IP to a data upon login.

While the Win2k machines report the real IP (ex: 12.1.1.34), the WinNT 4.0 machine will report 0.0.0.45, when the actually IP is 12.1.1.45. I'm using the winsock1.localIP command to return the machines' IP address. Anyone know what might be causing this. Is there a Winsock update I have to run on the WinNT 4.0 machines?

Thanks...

[jim mcnamara]

There was a big update for Winsock 2.0 that came out in late 1999.

I think NT 4.0 is at SP6a now. We stopped using 4.0 a while back, so I'm fuzzy on it. But there were some winsock 2.0 updates out in late 1999.

go here:

http://www.microsoft.com/ntworkstation/default.asp

[Evo]

try setting the BindAdress property of the winsock control on the NT machines to the Address you want the adapter to report
like:

Wsck1.bindaddress 203.147.123.144, 1001

cause it might be "binding itself" to another address.

hope this helps.