NLite windows build

[sub]

Can you post the output of "ipconfig /all"?

Windows is just choosing the wrong NIC when I ask for it to send a broadcast to 255.255.255.255. Reading up on this, it's apparently Windows just decides which device to use, and its awkward to force it to use another device (but I'm gonna have a go at it). I'd say this would would like effect other apps using multi-cast broadcasts.

Odd that Windows would be defaulting to your Virtualbox adapter.

[martint123]

The real network is the 2nd one. I don't know if I could force it to be number one in the list. Can you suggest another app that would use multi-cast and I could try it to see if it is affected as well.

Code:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : I5
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 0A-00-27-00-00-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f96d:738b:a8bc:2cc5%22(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.44.197(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 654835751
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-37-E5-64-90-2B-34-59-2D-90
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Qualcomm Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
   Physical Address. . . . . . . . . : 90-2B-34-59-2D-90
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1c45:ca40:56d2:896c%26(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 361769780
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-37-E5-64-90-2B-34-59-2D-90
   DNS Servers . . . . . . . . . . . : 208.67.222.222
                                       208.67.220.220
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::ac85:344e:e51d:7665%19(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.118.101(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 453005398
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-37-E5-64-90-2B-34-59-2D-90
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::58c:c421:2210:f427%20(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.244.39(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 469782614
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-37-E5-64-90-2B-34-59-2D-90
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Windows Adapter V9
   Physical Address. . . . . . . . . : 00-FF-B0-21-B5-BC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

[martint123]

Annoyingly now that it has worked, it is working all the time, even reverting to the original install file..........
I have done nothing to the network setting other than disbaling and then re-enabling the interface...... bloody computers

edit - could it have done techy things like setting up network routes that have stuck

[sub]

Odd. I'm not sure why anything would have changed.

Instead of just doing the broadcast to 255.255.255.255, I could force it to the broadcast address of a specific adapter, but then I'd have to actually look at your list of network adapters and make a decision between them - and it's not easy to tell which one I should use.

[mvallevand]

Shouldn't that be 255.255.255.0

Martin

[martint123]

If I do a TCP/IP reset with netsh int ip reset and a reboot then I get the original problem back i.e. nothing happens.
So it looks like windows remembers something once it has worked..... routes, mac address ??? - ask Bill.

'fraid I'm going to have to pack in for the night now.

Thanks again for the help.

[sub]

Shouldn't that be 255.255.255.0

Martin

No, I don't think so, and it is generally working for discovery.

[mvallevand]

Right I was thinking the netmask and not INADDR_BROADCAST address. In any case like martin123 mine won't connect to my backend but it does connect to a local instance. The problem is it connects to NextPVR on this adapter which is ok locally but it won't find

Code:

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::60d4:3f1:d5ca:a2ab%10
   IPv4 Address. . . . . . . . . . . : 192.168.56.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

I disabled this as a test and still no good because it connect on the IP of my laptops's internal nic which doesn't have a cable into it, I then disable that and it connected to my remote backend successfully.

FWIW it worth that test local instance of NRecord logs the same "bad" address

2016-10-10 19:16:52.235 [INFO][9] IP Address: 192.168.56.1
after disabling Vbox
2016-10-10 19:28:09.767 [INFO][9] IP Address: 192.168.99.1
and finally with both those disabled
2016-10-10 19:34:49.657 [INFO][9] IP Address: 172.16.3.55

Thinking about that one is wrong too, my wired NIC has a lower metric so it should have used another one. 3.62

Martin

[sub]

If I don't let Windows choose the appropriate device to broadcast on, then I'm going to have to manually choose it. Looking at martint123's ipconfig output, I can't see any information to help me decide which would be the real NIC (short of process-of-elimination, avoiding device with names containing VirtualBox/VMWare etc).

[sub]

Just to double check - was this problem happening on client sending the broadcast on the wrong NIC, or was the problem the IP address the server was replying with? (I couldn't see either of these potentially happening)