Two PCs, direct connection with ICS. Unidentified network.


Recommended Posts

Do to a temporary rearanging of things in the house, I've got two PCs connected with an eithernet cable sharing internet. One of them has a wireless card to connect to the router and it is sharing the connection with the other PC.

At first, it wouldn't work. Both PCs said the local area connection was unidentified. I noticed that they were on a different subnet. After some research, I learned that the unidentifed network issue is usually due to them not having a common gateway. I manually entered the IPv4 settings to put them on the same subnet and pointed one at the other as their gateway. Still didn't fix it. I then set everthing to defaults and magically after all the reboots and everthing, it started working.

Today, I wasn't getting a good enough signal to download some files quickly enough, so I ran a temporary line from PC2 (PC without wireless card), down the hallway to the router. After, when I hooked PC2 back up to PC1, I was back to having the original problem again. Now I can't get it working again.

Both are running Win7 Pro.

PC #1

Windows IP Configuration

Host Name . . . . . . . . . . . . : Upstairs
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-13-8F-89-79-2B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c16d:9d2e:b442:e59e%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.229.158(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 234886031
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-B2-88-D2-00-13-8F-89-79-2B

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{5CE07A93-112E-4335-BBCB-ADC9A493A2B4}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
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:

Media State . . . . . . . . . . . : Media disconnected
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
[/CODE]

PC #2 - the Linksys LNE100TX card is unused at the moment. Only using the interface on the mobo.

[CODE]Windows IP Configuration

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

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-14-BF-5C-73-54
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Network Bridge:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 02-0F-EA-47-1B-CA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c04c:2715:c4e1:92c3%18(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, August 15, 2012 6:27:59 AM
Lease Expires . . . . . . . . . . : Saturday, September 21, 2148 5:46:35 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 318902250
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-29-2B-DB-00-0F-EA-47-1B-CA

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

Tunnel adapter isatap.{4C5EA07A-652B-48B9-97D5-7B6019F18CEC}:

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

Tunnel adapter Local Area Connection* 12:

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:4137:9e76:3c32:2710:e7f0:6bd8(Preferred)
Link-local IPv6 Address . . . . . : fe80::3c32:2710:e7f0:6bd8%20(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{611A51AC-4BA0-4DF5-85E1-A0D4C314AD19}:

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

Tunnel adapter Local Area Connection* 13:

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

Right. PC #1 (named downstairs) has it's wired NIC and wireless NIC bridged. I've set the router to give it the static IP 192.168.2.100. It's always been that way, and I haven't messed with the router settings since way before this.

When things were miraculaouly working yesterday, PC #1 gave PC #2 the IP 192.168.2.114. With all NICs set to default settings to obtain IPs automatically.

"PC #1 gave PC #2 the IP 192.168.2.114. With all NICs set to default settings to obtain IPs automatically."

NO -- if you were bridged, then the Router your pc#1 is connected to would give the pc#2 its address and other dhcp info like mask and gateway and dns.

There is HUGE difference between ICS and Bridged interfaces.

So you have router --- wireless ---- PC#1 --- wired --- PC#2

dhcp scope on your router is

192.168.1.100 to 150

mask 255.255.255.0 or /24

gateway (itself) 192.168.1.1

dns (itself again or say opendns, googledns - whatever lets call it itself) 192.168.1.1

router is say 192.168.1.1, pc1 gets 192.168.1.100, pc2 would be 192.168.1.101

In a bridge (pc1) He sees packets on his interface 1, he sends it out interface 2, he sees packets on interface 2 he sends it out 1 - that is what a bridge does.

In ICS, your PC1 would be like a ROUTER, and doing NAT on the network he created on his 2nd interface. They are 2 different methods to accomplish pretty much the same thing. with ICS you would have something like this

router (192.168.2.1) ---- (192.168.2.100)PC1(192.168.1.1) ----(192.168.1.100)PC2

In that sort of setup PC1 would be the gateway for PC2, and the dhcp server and the DNS, just like your router is for PC1 -- where you can run into problems with ICS, is if you have duplicated networks on both interfaces of PC1. Depending on your OS version you would have to look up what the default IP of the ICS interface would be. In XP for example the ICS interface would have an IP address of 192.168.0.1. Not sure what it is in vista or w7 to be honest - might be the same.

I really don't play with ICS very often because a router cost like $20, there really is NO sort of configuration where ICS would be the desired setup.

If you need to extend a connection for example to another machine, like your setup where you have a wired connection to pc2 from pc1 and you want to share pc1 wireless interfaces network connection (internet) then sure bridging works just fine as a temp sort of solution until you can correctly setup your network where pc2 has its own actual connection to the network.

Delete the bridge and setup a ad-hoc between the two PC's to test the wireless you will need to setup the IP's manually.

Ok so the bridge is connected by wireless to your router with the bridge wired to the other PC...

Damaged cable maybe?

Like I said, this is a temporary situation. Normally everything is hooked up to the router. And I assumed since the machine was sharing it's connection with another, it was called ICS. I get the difference now. Thanks.

I still don't get why PC#1 isn't getting an address from the router.

This thread is good as any other to have a quick discussion on why you might pick ICS over Bridging or vice vesa, etc.

When you would want bridging:

Lets say you wanted to be able to do port forwarding to your devices that don't have their own connection to the network and are going to be connected via the bridging PC. What if you wanted to be able to see broadcast traffic on other devices directly connected to the routers network via wired or wireless. A bridge would put the clients all on the same network(broadcast domain) So your router could forward ports to them, your devices behind the bridge would be able to use UPnP to your gateway router, etc.

When would you want to use ICS over bridging.

Let say you had lots of devices that don't have a method to connect to the router - say no wireless interfaces. Or maybe your wireless device in the PC you were going to use to bridge does not like bridging and just doesn't work. If you wanted to isolate broadcast traffic from these 2 network, maybe you are going to have lots of traffic between clients, and don't want that traffic being sent onto the wireless network because it would eat up the wireless bandwidth. But your ok with just these clients internet traffic. And you only have a HUB to connect these other devices not a switch

For example in the above setup with PC1 bridging to his wireless network to a PC2, what if you had 5 other PCs that you wanted to have internet connectivity behind this PC1. And you stream say video or move large files between PC3 and PC5. You would not want PC1 sending all those packets onto the wireless network. And you were going to connect these other PCs to PC1 with a HUB. So PC1 bridge interface would see all this traffic and send it out his wireless interface.

Maybe you don't want broadcast traffic from these PCs behind PC1 to go out to the wireless network, maybe you don't want these PCs to be able to use UPnP on the router. Maybe you don't want PCs connect to the routers network to be able to access the other PCs behind PC1

In those types of cases then turning PC1 into a NAT router would make sense. You would have 2 different networks, you would have 2 different broadcast domains. There would be a NAT between network 1 and network 2, so that PCs connected to the router could not access PCs behind the NAT.

There lots of different reasons you might want to use ICS vs Bridging in a temp type of configuration to get something to work while you work out the final/correct setup.

But normally if its only 1 or 2 machines you need to connect to your routers network - and there is a PC that is connected then sure quick bridge of that PCs interface would be the fastest easiest method of getting these other PCs on the network and internet.

As to why PC1 isnt getting an IP?? Did you try doing a release and renew on it?

if you showing lights on the interface on your PC2 (bridge PC) - you could try setting static on PC1

give it say 192.168.2.101, 255.255.255.0, gateway 192.168.2.1, dns 192.168.2.1

Can you ping 192.168.2.100? Can you ping 192.168.2.1 ?? If not, what do you show in PC1 arp table after you try and ping

arp -a in cmd prompt on PC1

Maybe your wireless card just doesn't like bridging? Maybe you have a firewall on PC1 blocking DHCP?? There are **** load of reasons what you might be doing wrong.

edit: BTW to make your ipconfig /all easier to read - your clearly not using IPv6, so why don't just fully disable it so we don't see all that teredo/tunnel ****

from elevated cmd prompt

reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255

Above will fully disable IPv6, if you want to put it back to the way it is now - just delete the regkey with

reg delete hklm\system\currentcontrolset\services\tcpip6\parameters\ /v DisabledComponents /f

Then your output will look much cleaner. Here is my Box - even using IPv6 and its a lot cleaner looking ;)

post-14624-0-38049800-1345057738.jpg

I can ping both 192.168.2.1 and 192.168.2.100. Here is what I get when I run arp -a on PC1.


Interface: 192.168.2.105 --- 0xb
Internet Address Physical Address Type
192.168.2.1 bc-ae-c5-e7-d0-ce dynamic
192.168.2.100 00-18-39-0e-ec-a7 dynamic
192.168.2.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
255.255.255.255 ff-ff-ff-ff-ff-ff static
[/CODE]

Firewalls haven't changed. It was working for a few days. All I did was plug the cable into the router temporarily and then it wasn't working when I switched it back.

Changed PC1 to static

192.168.2.105

255.255.255.0

192.168.2.1 for gateway & dns

Could no longer ping 192.168.2.1 or 192.168.2.100. Destination host unreachable.

Arp table

[CODE]
Interface: 192.168.2.105 --- 0xb
Internet Address Physical Address Type
192.168.2.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.252 01-00-5e-00-00-fc static
[/CODE]

Interface: 192.168.2.105 --- 0xb

Internet Address Physical Address Type

192.168.2.255 ff-ff-ff-ff-ff-ff static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.252 01-00-5e-00-00-fc static

Well its never ever in a million years going to work if you don't have mac address of IPs in your table.

Lets be clear here on PC#

you say PC1 is Upstairs

and PC2 (bridge box) is Downstairs.

So its going to be a given that your bridge box PC2 can ping itself and gateway (router 192.168.2.1)

But your PC1 (non bridged box) Is not showing mac for router or even the mac for the interface the bridgebox its directly connected too.

So you got a bad cable? Its not doing autocross, or its not crossover - but until you can see the mac your never going to get to the router.

You said you were bridging the built in interface on the MB? I show 2.100 Mac

00-18-39 as Cisco-Linksys, and

bc-ae-c5 as ASUSTek COMPUTER INC <--- This is your router.

I dont think I have ever seen a cisco-linksys built in nic before? You sure you have the correct interfaces bridged?

Can you output your bridge setup using netsh

from cmd line do

netsh

you should then see

netsh>

then type bridge then show adapter and we should see your bridge configuration.

I can setup one real quick to show you the commands I am talking about in an example -- give me a few minutes

edit: Break your bridge, then output ipconfig /all then recreate your bridge and show the output of your netsh bridge show adapter command -- I will post example her in a minute or 2, my vm is booting.

edit2: ok here is before bridge - forget the ips for now


Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : local.lan
   Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter #2
   Physical Address. . . . . . . . . : 00-0C-29-53-2C-03
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.210(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, August 15, 2012 3:48:34 PM
   Lease Expires . . . . . . . . . . : Thursday, August 16, 2012 3:48:33 PM
   Default Gateway . . . . . . . . . : 192.168.1.253
   DHCP Server . . . . . . . . . . . : 192.168.1.253
   DNS Servers . . . . . . . . . . . : 192.168.1.253
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-53-2C-0D
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.41(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.253
   DNS Servers . . . . . . . . . . . : 192.168.1.253
   NetBIOS over Tcpip. . . . . . . . : Enabled

now in bridge

C:\Windows\system32&gt;ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : W7X64-VM
   Primary Dns Suffix  . . . . . . . : local.lan
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : local.lan

Ethernet adapter Network Bridge:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : MAC Bridge Miniport
   Physical Address. . . . . . . . . : 02-0C-29-53-2C-03
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Autoconfiguration IPv4 Address. . : 169.254.212.136(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Windows\system32&gt;netsh
netsh&gt;bridge
netsh bridge&gt;show adapter

----------------------------------------------------------------------
ID AdapterFriendlyName		 ForceCompatibilityMode
----------------------------------------------------------------------
  1 Local Area Connection 2	 unknown
  2 Local Area Connection	   unknown
----------------------------------------------------------------------

edit: as I mentioned before some wireless cards don't like bridge mode, they need to support Promiscuous Mode

http://support.microsoft.com/kb/302348/en-us

Bridge May Not Work With a Non-Promiscuous Mode Network Adapter

You said you were bridging the built in interface on the MB? I show 2.100 Mac

00-18-39 as Cisco-Linksys, and

bc-ae-c5 as ASUSTek COMPUTER INC <--- This is your router.

I dont think I have ever seen a cisco-linksys built in nic before? You sure you have the correct interfaces bridged?

00-18-39 is the wireless on PC2, which is a Linksys. That's what I want, right? The PC1 connected to the LAN on PC2, and the LAN and wireless on PC2 bridged so that PC1 gets internet.

Broke bridge. PC2 config:


Windows IP Configuration
Host Name . . . . . . . . . . . . : Downstairs
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys LNE100TX(v5) Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-14-BF-5C-73-54
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Network Bridge:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 02-0F-EA-47-1B-CA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : 00-18-39-0E-EC-A7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.2.114(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, August 15, 2012 7:41:42 PM
Lease Expires . . . . . . . . . . : Sunday, September 22, 2148 2:15:23 AM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0F-EA-47-1B-CA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.229.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 169.254.229.100
NetBIOS over Tcpip. . . . . . . . : Enabled
[/CODE]

Recreated bridge.

[CODE]
netsh>bridge
netsh bridge>show adapter
----------------------------------------------------------------------
ID AdapterFriendlyName ForceCompatibilityMode
----------------------------------------------------------------------
1 Wireless Network Connection unknown
2 Local Area Connection unknown
----------------------------------------------------------------------
[/CODE]

Then how do you still have a Bridge listed in your output? Did you create multiple bridges? Delete all bridges shown in Control Panel\Network and Internet\Network Connections

Then recreate it, and I would put your wireless adapter

netsh bridge set adapter X forcecompatmode=enable

http://support.microsoft.com/kb/302348/en-us

edit: Break your bridge, then output ipconfig /all then recreate your bridge and show the output of your netsh bridge show adapter command -- I will post example her in a minute or 2, my vm is booting.

That's what I did. The bridge is showing enabled because I enabled it before doing the netsh bridge show adapter.

Odd that a bridge would stay with no members - easy way to break a bridge is to just delete it, that would of been my method. But sure ok, my bad.

So set the forcecompatmode=enable on your wireless interface and see if that helps. Again some wireless just do not like to bridge, they have to support promiscuous mode, etc.

its hard for me to do remote, but I can recreate what your trying to do when I get back to the house. But tonight is BEER night, so not sure when that will be ;)

If you can not get the bridge mode to work, then go the ICS route - that should work even if your wireless does not support bridge mode.

Deleted bridge


Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : 00-18-39-0E-EC-A7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.2.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, August 16, 2012 10:16:05 AM
Lease Expires . . . . . . . . . . : Sunday, September 22, 2148 4:50:40 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0F-EA-47-1B-CA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.229.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 169.254.229.100
NetBIOS over Tcpip. . . . . . . . : Enabled
[/CODE]

Recreated bridge

[CODE]
----------------------------------------------------------------------
ID AdapterFriendlyName ForceCompatibilityMode
----------------------------------------------------------------------
1 Wireless Network Connection unknown
2 Local Area Connection unknown
----------------------------------------------------------------------
[/CODE]

I don't see how my wireless adapter would have a problem with bridge when it worked flawlessly for the few days until I unplugged the cable.

Also did forcecompatmode=enable, but nothing has changed.

I don't know either, for all we know you were using ICS before?? I can not troubleshoot what I can not see, the heading of this thread is ICS, but your talking bridging. So to be frank - I have no idea what you were doing before

But what I can tell you is the wireless card does need to support promiscuous mode - and from your bridge output, its not known if its in that mode or not? So you could try setting it.

If that does not work - then use ICS mode. Unless you have a NEED to port forward traffic from your router to the box behind your PC connected to your netework the box behind the bridge or the ICS would have little difference in accessing normal stuff on the internet.

But it was never ever going to work from what you posted before with the box behind not showing MAC for the gateway IP.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Dupe of "Microsoft further improving Windows 11 Taskbar with latest builds", published <20 minutes apart
    • Dupe of "Windows 11 is getting redesigned taskbar settings in new build", published <20 minutes apart
    • Ooooh! Two editorial from Paul Hill on the same day! Is it my birthday or something? 😉 Okay, let's see if I get it right. SearXNG develops a meta-search engine app. Individuals install it on their relays. Users connect to these relays to have their own identity-stripping meta-search engine instead of relying on DuckDuckGo. And some of these volunteers have listed their SearXNG instances on SearX.space. That was a lot of wrap my head around. I hope I haven't missed anything.
    • You sound like some Ukrainians in Crimea before 2014: "I didn't vote for USSR disbanding - I want Ukraine to be part of Russia again" 🤣
    • Uninstalr 3.1 by Razvan Serea Introducing Uninstalr: Easy to use and very accurate software uninstaller for Windows. It can uninstall multiple apps at the same time and we think it’s pretty cool. Developed with expertise by Macecraft Software - the minds behind jv16 PowerTools. Key Features Batch uninstall many apps at the same time. Supports unattended uninstallation of apps. Supports monitoring of new software installations. Also detects portable apps and previously uninstalled software leftovers. Shows all the data added to your system by installed software on a file by file basis. Shows all the data it will remove before starting the uninstallation. Filter and search the list of installed software. According to our benchmark, Uninstalr is the most accurate software uninstaller by leaving the least amount of leftovers when uninstalling apps. Supports detection and uninstallation of Microsoft Store, Steam, Big Fish Game System, Chocolatey, NuGet and Ninite installed software. Supports Windows Dark Mode. Supports Windows 11, 10, 8 and 7. Comes with these translations builtin: Chinese Simplified, Chinese Traditional, Czech, Danish, English, Filipino, Finnish, French, German, Greek, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Romanian, Slovak, Spanish, Swedish, Thai, Turkish, Ukrainian and Vietnamese. Has a single executable file portable version and a normal setup version. Uninstalr is freeware, lightweight and easy to use. No bells and whistles, no nonsense. Uninstalr’s custom uninstallation engine has a dedicated support for the detection and uninstallation of 15 types of apps: Normal Windows apps Microsoft Store apps Portable apps Chocolatey apps Ninite apps PortableApps.com apps Steam games EA App games Epic Games Store games Riot platform games GOG Galaxy games WarGaming.net games Battle.net games itch.io games Big Fish platform games Uninstalr 3.1 changelog: Key Changes Uninstalr now starts and shows the list of installed apps faster after the initial scan has been completed, and with much smaller memory usage. Uninstalr now detects and highlights apps that automatically start with Windows. Greatly improved the detection of portable apps. Improvements New feature: Uninstalr now detects and highlights apps that automatically start with Windows. New feature: Uninstalr now highlights possible leftovers and apps from Russia and China. This can be disabled from the Settings. New feature: A new filter that allows you to show only software that is installed to other than the system drive. New feature: Users can now select to always do the deepest and the most accurate scan for installed apps, at the cost of the analysis taking a longer time. Greatly improved the detection of portable apps, such as added dedicated support for MiTeC, EZ Tools and SysInternals tools. Improved support for portable apps installed via Windows System Control Center (WSCC). NirSoft portable apps are now listed with "NirSoft" prefix for easier identification. Improved the speed of uninstalling apps. The main installed software listing search will now find "Xbox GameBar" if you search for "Game bar" and vice versa. The tooltip now displays more detailed information of the installed apps, such as its registry key and uninstaller path. The links in the About section now look more like clickable links. The main menu is now more clearly indicated in the main user interface. Microsoft Teams Meeting Add-in for Microsoft Office ships with some Windows 11 installations and is now considered a builtin Windows app and only listed if builtin Windows apps filter is enabled. Added a Help button to the main user interface that opens the help section of the website. Added an option not to close Uninstalr after uninstallation. If you open the Uninstalr website from the app, the website now receives the version number of your current Uninstalr version and warns you if you are using anything but the latest version. Improved the accuracy of the New Software Monitor. Improved confirmation messages for Steam and other platform related uninstalls. Improved the uninstallation performance of Steam games. Fixes: Known bug fixed: Some installed app names are capitalized incorrectly, such as "CCleaner Portable" is listed as "ccleaner portable". Known bug fixed: Some apps can be listed twice, for example, Smart Defrag can be listed once as Smart Defrag and then Smart Defrag Home. Known bug fixed: On the pre-uninstallation screen, the Scripts checkbox can be checked by default on Dark Mode but not on the normal mode. Known bug fixed: Perform Deep Analysis can be started only by clicking the button, not via the Right Click menu, main menu or F4 keyboard shortcut. Muse Hub could be incorrectly listed as Adobe Muse. SyncTrayzor was incorrectly detected as two unrelated software, SyncTrayzor and Syncthing. Smart Defrag was incorrectly listed twice as Smart Defrag 11 and Smart Defrag Home. It was possible to enter non-printable characters to the search input boxes of the main screen, and the path listing screen, which caused the UI to look funny. Changing the translation from Settings, especially many times in a row, caused the UI to distort. If you had multiple instances of portable apps on your system, such as the 64b and 32b versions of the same portable app, typically only one of them was detected, not both. In some very rare cases, Uninstalr UI could start with random characters in its search input boxes, which could make the UI look rather confusing. This was a rare issue, only reported by two users. The pre-uninstallation screen could display non-existing paths for example as the software's installation directory or main exe file. This was a cosmetic issue. New Software Monitor cannot detect the installation of Claude. Selecting all the found software made the UI look funny with the top panel covering everything else (because the names of all the selected software were listed there). Sometimes a Steam game could be listed a normal app instead of a Steam game. If the system restart after an uninstallation is delayed, e.g. because of Windows Updates being installed, this additional delay is incorrectly added to the time how long the uninstallation process took. This cosmetic bug could cause the program incorrectly report an uninstallation time longer than the actual uninstallation time. Uninstalling Minecraft could simply fail. The Only scan the system drive for installed apps setting does not fully work. If some apps are installed to a non system drive and this setting is enabled, the app could still be detected and listed on the main user interface. Changing any settings could also incorrectly alter the Only Scan The System Drive For Installed Apps setting. Microsoft OneDrive and Copilot are not always detected. If you enter something to the search filter field, then select the text and press the Delete key, this triggers the Uninstall button click even if your intent was to delete the text input. If you press the F5 key to refresh the screen during the uninstallation loading screen, the program will crash. If you enabled some setting, such as "Do not analyze installed app installation sizes", it could automatically be unchecked later. Uninstalr doesn't warn you if you try to remove Fortec antivirus. There should be a warning if user attempts to remove any antivirus or antimalware type program. Such programs should not be uninstalled using a third party uninstaller, as they are typically protected against automated uninstallation, for security reasons. With "Do not analyze installed app installation sizes" option checked from the Settings, Uninstalr could still display some installation size related elements in the UI which was confusing. The "Only scan the system drive" option moved under Improve Scan Speed from the General settings. If two software have the exact same name and version number, selecting both of them for uninstallation fails because only one is actually selected. Sorting the installed apps by size sometimes fails and the order is incorrect. The "Don't show which paths are currently analyzed" did not work correctly - some parts of the UI still show the currently analyzed path with this setting checked. The "Don't list software less than 10 MB" filter did not work correctly - some apps smaller than 10 MB could still be listed. Uninstalr could start very quickly and display an empty list of detected apps. Restarting the app usually fixed the issue and the list of installed apps was properly displayed. If you placed portable Uninstalr to a same folder with other portable apps, those were not detected because Uninstalr automatically added its installation folder to the ignore list. When trying to uninstall some specific software, Uninstalr could get stuck on the Searching for more data relating to the app phase. Uninstalr could sometimes do a silent uninstallation even if user had unchecked the Perform a silent uninstallation option. Known issues: Uninstalr can fail to run with an Out Of Memory error in systems that have a lot of installed apps. Using the New Software Monitor tool multiple times during one session can cause the program to get stuck on the Scanning stage. The "uninstallation completed" message box sometimes closes when the user moves the mouse cursor over the button before user clicks it. There is no feedback for the user after Fix Information feature has been used. The Right Click menu's Select by publisher option can display the number of apps per each publisher without correct vertical alignment. The default user interface might not display all of the found installed apps if you have over 600 installed apps. If you do, using the Screen Reader Compatible Interface solves the issue. Leftover apptype filter checkbox is shown in red font only in Dark Mode. Clicking the app's icon from the Windows Taskbar doesn't minimize/restore the app like other apps. The warning about an app that user wishes to uninstall being related to some other app user did not select can sometimes be inaccurate. If app's language is changed without restarting Uninstalr, the list of installed software might not automatically refresh. When software is being uninstalled, the UI can say it is processing paths unrelating to the uninstalled app. This is purely cosmetic and does not mean these paths are removed. Uninstalr might not properly detect and/or uninstall Steam games if they are installed to a drive different than Steam's default location in C:\. You might see "This action is only valid for products that are currently installed" error message from Windows Installer during uninstallation. This is a cosmetic issue. Download: Uninstalr 3.1 | 7.1 MB (Free, paid version available) Download: Uninstalr Setup 3.1 View: Uninstalr Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      153
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!