Windows Server 2008 R2 x64 can't bind socket

Mimiko

Well, on trying to move to x64 system encountered a strange problem. All the configs and files are taken from working Windows 2003 x32, except for the TAP-driver part. In the server config:

dev tun
server 192.168.3.0 255.255.255.0
management tunnel 7505

The OpenVPN start-ups well, sets IP, sets routes and then:

14:23:37 2011 Initialization Sequence Completed
14:23:37 2011 MANAGEMENT: Socket bind failed on local address 192.168.3.1:7505: The requested address is not valid in its context.
14:23:37 2011 Exiting

It's not that 7505 is used by something else. As states microsoft: the IP 192.168.3.1 was not found on any adapter, that's why it can't bind. But that's not possible, as before Initialization complete the route add 192.168.0.0 mask 255.255.255.0 gw 192.168.3.2 was done added with success. After sleep, all settings, and routes to the system are added in less than a second - ie very quick. May be the management just starts to bind too quickly?

maikcat

stupid question,

why do you want your managment interface listens to the tun interface?

Michael.

Mimiko

why do you want your managment interface listens to the tun interface?

Well, for clients it ables to control something remotelly, even if there is some problem on setting up the connection. Or, when in the client's config is "management-hold" I suppose that the unhold command can be done from server's management.
On server I really don't need to listen on the tunnel, but also I don't whant to specify the interface or IP on which management will listen, I want that management will listen on all interfaces installed on computer and the access will be restricted with a firewall. But from manual, the IP is mandatory to the "management" option.