Could not bind socket. Address and port are already in use

[blisk]

Hi,

Here is my problem:

With the Labview installed (8.5 or 8.6.1), I can't make a connection to some specific DDC controller (SE elektronik). The connection is via ethernet cable.

When I try to make a connection, the massage appears: "Could not bind socket. Address and port are already in use."

This happens also if I don't have Labview opened and with XP or Vista.

When I uninstall Labview, the communicatin is o.k.

I'm thankig you for any help.

Best regards,

Zdenko.

Message Edited by blisk on 03-28-2009 04:46 AM

[CoastalMaineBird]

When I try to make a connection

What sort of connection are you talking about?

TCP, UDP, DataSocket? 

[blisk]

It is TCP.

Beast regards,

Zdenko.

[CoastalMaineBird]

When I uninstall Labview, the communicatin is o.k.

You're going to have to spend some words and describe your problem - otherwise, we don't know what you're talking about.

For example, what program is it that's reporting an error, if LabVIEW is not installed?

[blisk]

Hi,

This is a specific programm for programming DDC controllers from company SE-elektronic.

In the programm there is no options to adjust any communication parameter.

DDC controller have a IP address 192.168.0.1.

It runs perfect when a Labview is not installed.

With a Labview installed, the massage "Could not bind socket. Address and port are already in use" appears.

Best regards,

Zdenko. 

Message Edited by blisk on 03-29-2009 11:45 AM

[CoastalMaineBird]

DDC controller have a IP address 192.168.0.1.

Typically, 192.168.0.1 is used for the router itself on a LAN, and thus shouldn't be used by other devices.

A Streamwatcher trace on my system shows lots of UDP traffic on 192.168.0.1: 53, which is DNS lookup activity. 

There's also activity to 192.68.0.1: 1900 when LabVIEW starts up / shuts down. 

This traffic goes to 239.255.255.250: 1900 - I don't know what that is. 

What is your router address?

What port is the device on?

Try this test:

With the device working (without LabVIEW), open a browser and surf around a bit.

Do you get any "could not find" messages in the browser?

(if the device s interfering with DNS, it's show up,)

[blisk]

Thanks,

I think the problem is not connected with the controllers IP address. ( it can be changed, but the problem still exists). 

To test, I don't have to physically connect a DDC controller.

When I start program (it calls Workprogramm), I chose "network". And a massage "Could not bind socket. Address and port are already in use" immediately appears.

I tried on two different computes, with Windows XP and Vista.

A Labview program even don't have to run.

I can e-mail you this programm if you are willing to test it.

Best regards,

Zdenko

Message Edited by blisk on 03-29-2009 12:49 PM

[CoastalMaineBird]

I think the problem is not connected with the controllers IP address. ( it can be changed, but the problem still exists). 

But if the program itself cannot be changed, then it doesn't matter.

You said earlier: In the programm there is no options to adjust any communication parameter.

If the program is TRYING to communicate on a given address / port, it doesn't matter whether the other end is there or not, the port will be busy.

If you're on Windows, then I know that LabVIEW has licensing stuff that might be phoning home (I don't know this for a fact).  Possibly that would be why if LV is merely INSTALLED, the problem occurs. 

But the root problem comes down to why is the program using the same address as the router (if what I suspect is true). 

[blisk]

Thanks,

I have run programm on laptop.

A laptop is not connected to any network.

I changed IP address for LAN and WLAN.

The problem still exist.

Any idea what else to try?

Best regards,

Zdenko.