Can't make bridging work on Windows 8.1 x64 pro

Started by DarkUltra

Can't make bridging work on Windows 8.1 x64 pro   20 March 2014, 06:41

Hi!

I can't seem to get this going, bridging on a Windows 8.1 Pro 64bit. I have tried two different configurations.

One with static ips:
cable modem - dlink dir 655 router (gateway 192.168.0.1) - (192.168.0.2 static) pc with BWM and two NICs as bridge (static 192.168.0.3) - switch - (192.168.0.4 dhcp mode but error message if I try to renew) lan computer
route -p add 192.168.0.1 mask 255.255.255.255 192.168.0.2

also with dhcp dynamic ip from dlink router:
cable modem - dlink dir 655 router (192.168.0.1) - (192.168.0.95 dhcp from dlink router) pc with BWM and two NICs as bridge (static 192.168.0.98) - switch - (192.168.0.4 dhcp mode but error message if I try to renew) lan computer
route -p add 192.168.0.1 mask 255.255.255.255 192.168.0.95

both cases removed gateway from nic2.



Here is ipconfig /all from

Bridging PC (Arne):
Windows IP Configuration

   Host Name . . . . . . . . . . . . : Arne
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : getinternet.no

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ether
net Controller
   Physical Address. . . . . . . . . : 00-16-E6-5E-04-FA
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4ce5:7b9:bf2f:6515%4(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.98(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 117446374
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-AE-11-79-00-0E-0C-38-71-84

   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:

   Connection-specific DNS Suffix  . : getinternet.no
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 00-0E-0C-38-71-84
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3090:88e3:6652:ac8a%3(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.95(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 19. mars 2014 20:15:22
   Lease Expires . . . . . . . . . . : 20. mars 2014 20:15:22
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 50335244
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-AE-11-79-00-0E-0C-38-71-84

   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.getinternet.no:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : getinternet.no
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{FCDFA1EE-8F5F-4217-A243-9627F20C01EA}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes




Local PC (Gaara):
Windows IP Configuration

   Host Name . . . . . . . . . . . . : Gaara
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : getinternet.no

Ethernet adapter Local:

   Connection-specific DNS Suffix  . : getinternet.no
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 54-04-A6-35-8D-7D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3ce4:510a:968b:a027%5(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.96(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 19. mars 2014 20:28:24
   Lease Expires . . . . . . . . . . : 20. mars 2014 20:28:23
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 223610022
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-47-71-37-54-04-A6-40-65-E7

   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.getinternet.no:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : getinternet.no
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:84:320d:ab2f:389f(Prefer
red)
   Link-local IPv6 Address . . . . . : fe80::84:320d:ab2f:389f%7(Preferred)
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 150994944
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-47-71-37-54-04-A6-40-65-E7

   NetBIOS over Tcpip. . . . . . . . : Disabled




Bridging (Arne) PC routing:

===========================================================================
Interface List
  4...00 16 e6 5e 04 fa ......Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Contr
oller
  3...00 0e 0c 38 71 84 ......Intel(R) PRO/1000 MT Desktop Adapter
  1...........................Software Loopback Interface 1
  5...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
  6...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.95    200
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.0.0    255.255.255.0         On-link      192.168.0.98    306
      192.168.0.0    255.255.255.0         On-link      192.168.0.95    356
      192.168.0.1  255.255.255.255     192.168.0.95     192.168.0.98     51
      192.168.0.1  255.255.255.255         On-link      192.168.0.95    101
     192.168.0.95  255.255.255.255         On-link      192.168.0.95    356
     192.168.0.98  255.255.255.255         On-link      192.168.0.98    306
    192.168.0.255  255.255.255.255         On-link      192.168.0.98    306
    192.168.0.255  255.255.255.255         On-link      192.168.0.95    356
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.0.95    356
        224.0.0.0        240.0.0.0         On-link      192.168.0.98    306
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.0.95    356
  255.255.255.255  255.255.255.255         On-link      192.168.0.98    306
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      192.168.0.1  255.255.255.255     192.168.0.95       1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  3    266 fe80::/64                On-link
  4    266 fe80::/64                On-link
  3    266 fe80::3090:88e3:6652:ac8a/128
                                    On-link
  4    266 fe80::4ce5:7b9:bf2f:6515/128
                                    On-link
  1    306 ff00::/8                 On-link
  3    266 ff00::/8                 On-link
  4    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None



Uhm could it be that the bridge is greyed out?
SoftPerfect support forum
SoftPerfect Support forum - Andrew avatar image

Re: Can't make bridging work on Windows 8.1 x64 pro   20 March 2014, 12:09

The configuration appears to be correct. Assuming, it's all connected like this:

<Router/192.168.0.1> - <192.18.0.2/Arne/192.168.0.3> - <192.168.0.96/Gaara>

Can you ping 192.168.0.3 and 192.168.0.1 from Gaara?

I understand that DHCP fails for some reason, but if IP addresses are assigned manually, does the ping work?

Re: Can't make bridging work on Windows 8.1 x64 pro   21 March 2014, 05:42

DHCP kinda works, I reset the dhcp client list and Gaara did get a new IP, but If I renew it I get:

An error occurred while renewing interface Arne : unable to contact your DHCP server. Request has timed out.

PS! Now local client Gaara has ip 192.168.0.97


Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.0.97: Destination host unreachable.
Reply from 192.168.0.97: Destination host unreachable.

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),



Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.97: Destination host unreachable.
Reply from 192.168.0.97: Destination host unreachable.
Reply from 192.168.0.97: Destination host unreachable.
Reply from 192.168.0.97: Destination host unreachable.

Ping statistics for 192.168.0.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),



I can ping LAN nic2 of bridge pc:

Pinging 192.168.0.3 with 32 bytes of data:
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128
Reply from 192.168.0.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

I tried connecting the Bridge PC directly to the internet and then local PC does get both an IP and internet access. Maybe it is my router Dlink DIR 655 that is problematic?
SoftPerfect Support forum - Andrew avatar image

Re: Can't make bridging work on Windows 8.1 x64 pro   21 March 2014, 17:16

Yes, it's quite strange and may be a router issue.

I would probably recommend to try with a different router.

Re: Can't make bridging work on Windows 8.1 x64 pro   22 March 2014, 00:36

More findings. I did this with the router:

disabled port 80 forwarding to 192.168.0.2
disabled SPI
NAT udp and tcp set to endpoint independent

disabled dns relay
disabled Always broadcast dhcp

The last two did it I think.

Local PC can now connect to internet.
However cannot connect to router or bridging PC and I have to re-create the bridge in bandwidth manager if I reboot the briging PC.

Re: Can't make bridging work on Windows 8.1 x64 pro   11 April 2014, 17:04

I had problems with an earlier version 3 of SoftPerfect Bandwidth Manager and win 8 64bit with bridging.

Think every time I rebooted I lost the bridge or something but it was unreliable so I went back to Win 7 64bit.

Going to give 8.1 64bit with bridging and version 3.0.6 a go.

I'll report back after I try.

Re: Can't make bridging work on Windows 8.1 x64 pro   12 April 2014, 09:18

Just tested 3.0.6 (in Bridging mode) with win 8.1 64bit (not the 8.1 update) and all seems well until you restart the pc.

After restart, BWM doesn't let any traffic through to internet. LAN seems to work because LAN pc's were getting DHCP and DNS requests from simple DNS.

Checked bridging and it was still there.

Restarting BWM service got it going again.

Restarted a few times and exactly the same scenario, with restarting the BWM service (after PC restart) allowing traffic through to net.

Setup:

LAN PC's (192.168.9.***>Switch>PC running BWM (in Bridge mode [LAN side 192.168.9.108 Modem side 192.168.9.109]) and Simple DNS>Router/Modem (192.168.9.101)

Works fine Win 7 64bit

Re: Can't make bridging work on Windows 8.1 x64 pro   13 April 2014, 08:18

Just tried delayed start for BWM service in services and it seemed to work OK after reboot.
SoftPerfect Support forum - Andrew avatar image

Re: Can't make bridging work on Windows 8.1 x64 pro   13 April 2014, 12:16

Thanks for the info.

It appears that the network cards aren't quite ready yet if the delayed start helps.

I will change the installer to configure the service for delayed startup by default.
Hi,
I have this problem too (Bridge stop working after restart) but my bigger problem is delay service start didn't solve my problem, every time I restart my server I have to reconfigure my bridge to work, when I'm not here (my company) at morning all of client will be down until I came to reconfigure bridge.

Anyone have any idea???
SoftPerfect Support forum - Andrew avatar image

Re: Can't make bridging work on Windows 8.1 x64 pro   09 June 2016, 16:24

This might occur if some some reason the adapter's GUID changes between reboots, which should not normally be happening.

You can find out if that's the case by typing netsh lan show interfaces in a command prompt before and after bridge becomes inactive and post the dumps here.
Thank you for response,

After windows start

Name             : Ethernet 2
Description      : D-Link DGE-528T Gigabit Ethernet Adapter
GUID             : 563643bf-3dd9-4a3f-b414-e196fd8b605f
Physical Address : C4-12-F5-32-20-BB
State            : Attempting to authenticate

Name             : Ethernet
Description      : Realtek PCIe FE Family Controller
GUID             : 7f18ae16-6439-413d-a23f-c8a4fe462896
Physical Address : 00-1F-D0-1E-3A-39
State            : Attempting to authenticate

After reconfigure bridge

 Name             : Ethernet 2
 Description      : D-Link DGE-528T Gigabit Ethernet Adapter
 GUID             : 563643bf-3dd9-4a3f-b414-e196fd8b605f
 Physical Address : C4-12-F5-32-20-BB
 State            : Connected. Network does not support authentication.

 Name             : Ethernet
 Description      : Realtek PCIe FE Family Controller
 GUID             : 7f18ae16-6439-413d-a23f-c8a4fe462896
 Physical Address : 00-1F-D0-1E-3A-39
 State            : Connected. Network does not support authentication.

My windows is 2012R2 (which have same platform as 8.1)
SoftPerfect Support forum - Andrew avatar image

Re: Can't make bridging work on Windows 8.1 x64 pro   09 June 2016, 17:34

Thanks, but I needed the dumps between system restarts (not before and after starting BM) as I suspect the adapter GUIDs may change across reboots.
So could you tell how I can get what you want to know?
because i'm not really pro on bridge staff, my expertise is in domain so please let me know what I can do to get that report which you want
SoftPerfect Support forum - Andrew avatar image

Re: Can't make bridging work on Windows 8.1 x64 pro   09 June 2016, 19:03

Just do netsh lan show interfaces once when bridge is OK. Then reboot and check if the bridge is broken in BM. If that's the case, run the command again and post the dumps here.
This is before restart when bridge work fine

 Name             : Ethernet
 Description      : Realtek PCIe FE Family Controller
 GUID             : 7f18ae16-6439-413d-a23f-c8a4fe462896
 Physical Address : 00-1F-D0-1E-3A-39
 State            : Attempting to authenticate

 Name             : Ethernet 2
 Description      : D-Link DGE-528T Gigabit Ethernet Adapter
 GUID             : 563643bf-3dd9-4a3f-b414-e196fd8b605f
 Physical Address : C4-12-F5-32-20-BB
 State            : Attempting to authenticate

And this result is for when I restart server and wait for 10 min after that I used netsh command, bridge is not working right now


Name             : Ethernet 2
Description      : D-Link DGE-528T Gigabit Ethernet Adapter
GUID             : 563643bf-3dd9-4a3f-b414-e196fd8b605f
Physical Address : C4-12-F5-32-20-BB
State            : Attempting to authenticate

Name             : Ethernet
Description      : Realtek PCIe FE Family Controller
GUID             : 7f18ae16-6439-413d-a23f-c8a4fe462896
Physical Address : 00-1F-D0-1E-3A-39
State            : Attempting to authenticate
SoftPerfect Support forum - Andrew avatar image

Re: Can't make bridging work on Windows 8.1 x64 pro   11 June 2016, 18:00

Thanks, apparently GUIDs aren't the issue as they don't change.

Could you please export your ruleset to a .DB file, compress it and upload to our support area? We'll continue troubleshooting there.

Sometimes you can get the answer faster if you try the forum search and/or have a look at the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

  ******   **    **  **         **     **        ** 
 **    **  ***   **  **    **    **   **         ** 
 **        ****  **  **    **     ** **          ** 
 **        ** ** **  **    **      ***           ** 
 **        **  ****  *********    ** **    **    ** 
 **    **  **   ***        **    **   **   **    ** 
  ******   **    **        **   **     **   ******  

Message: