Donate Share

BACnet Protocol Stack

The forum address has changed, you have been automatically redirected. Please update any bookmarks to use the new URL.

Subscribe

Windows XP bind to specific Interface

You are viewing a single message from this topic. View all messages.

  1. 2009-06-19 12:51:49 UTC
    Hi,

    first of all I have to say the more I work with Bacnet the more I like it.
    I don't see myself as a developer and for my purposes the demo applications work fine for me.
    But now I ran into a problem at a XP-machine with several Ethernet-Interfaces. They are all in use with differen IPs.
    Problem I have is that bacrp.exe (or any other program) binds to another interface I actually want to comunicate to.

    Setup:
    IF1: 10.0.0.1
    IF2: 192.168.0.1

    I want to read from a device with IP 10.0.0.100.
    I get Error: APDU Timeout!
    With wireshark I could see that bacrp.exe has bind to IF2 and send with IP 192.168.0.1 and never gets an answere.
    Only solution I found so far was disable IF2 and it works.

    My question is, is it possible to make any of this programs bind to IF1 directly?

    Thanks in advance
< Previous | 1 | Next >

Add a Reply

This forum does not allow anonymous participation.

Log in to add a reply. Not registered? Create an account to participate and receive email updates when replies are posted to this topic.