Jan Just Keijser wrote: > > So XP is refusing port 445 connections from OpenVPN adapter. > > Maybe someone on the -devel list (CC'ed) knows more about the > interaction between the tap-win32 adapter and the rest of the > windows os?
This reminds me of my experience with pushing a DNS server address as part of the VPN connection. I was using a configuration where traffic to the DNS server always needed to be routed. It was not directly reachable on any client interface. After the DHCP client for e.g. a LAN or wifi connection in Windows has been configured with a DNS server, the DNS resolver would bind to the underlying interface that was configured by DHCP. Even if the OpenVPN server pushes another DNS server setting which is applied to the system when bringing up the TAP adapter, the DNS resolver was still "bound" to the underlying interface and DNS lookups would now fail. (The new IP was firewalled to only be reachable via VPN.) (My solution was to make the DNS server always be on the same IP network as the underlying interface.) This seems to have nothing to do with incoming port 445 traffic, but maybe something similar is going wrong? You could try to stop and then start the service responsible for listening on that port. I'm not quite sure which one it is though. Stopping and starting the DNS resolver helped in my situation, but wasn't an adequate fix. At least it might provide you with some more information. Kind regards //Peter
