Network Path Not Found... The Windows XP - Windows 7 Networking Hell


Recommended Posts

Just bought a new Gateway NV53 laptop with Windows 7. I have a desktop upstairs that's a Windows XP machine, and an older HP model laptop that's Windows Vista.

I connected my laptop to the wireless network, was able to instantly access my old laptop with Vista. Windows XP machine didn't show up. Google'd some help, changed all the workgroup names to the same name, set the network to a work network on my Windows 7 machine.

I can't access the XP machine despite having it show up as an icon. I also cannot ping that machine from my Windows 7 machine. I can ping the XP machine from the router, so that isn't a problem. I assumed this was a firewall problem, but I turned everything off.

DOS continues to say Destination is Not Reachable for the IP address. I tried everything. Enabling NETBIOS settings, Winsock XP fix, etc.

I still can't ping the machine or access it.

Any help would be appreciated.

^ Who ever wrote that article is a MORON!!! Plain and simple -- LLTD has NOTHING do with accessing file shares off a computer.. All that does is allow vista win7 to correctly place the xp box on its pretty much pointless eyecandy network map.. Which has NOTHING do with file sharing - NOTHING!!

Lets get down to basics for your problem.. You say you can not ping the XP box from your win7 machine.

Is the XP box wireless or wired? What about the vista machine - is it wired or wireless? Can you ping the xp box from the vista machine?

Wireless to wireless could be security feature on your router called Isolation mode that prevents wireless clients from talking to each other.

Lets get your pinging working first so we are sure you have connectivity -- then will worry about file sharing access.

So lets understand your clients -- which one are wired, which ones are wireless.. etc.. For troubleshooting I would suggest you put everything on the wire.. Once that works then you can move a client to wireless. Is your router using any sort of mac filtering? Does it support lan to lan firewall rules? What model of wireless router do you have?

BTW -- same workgroup has NOTHING do with with accessing file shares either.. Sure it can make it easy and faster for browsing to correctly populate -- but is meaningless when looking to ping or share files..

If you can not ping, you either have a firewall issue - or you got some other networking issue going on -- which if the case your never going to get file sharing to work.. So I would suggest you get ping working first.

When you try to ping your xp box, you say you get not reachable vs time out.. So I would assume your not finding the mac of the xp box.

From a command line on your xp box -- do an ipconfig /all -- it will list the mac address for its interfaces - be it wired or wireless..

Now on your win 7 machine - after you try and ping look at your arp table - you should see the xp machines mac address listed, even if there was some firewall on the xp machine preventing ping - you should still get the mac.. if its all zeros for the mac, then you got a issue that is not related to LLTD or workgroup that is for sure.

You could try setting a static arp table entry for the xp box ip on the win 7 box -- can you ping it then?

you can view your arp table on win 7 with arp -a -v will show you all the entries in your table even the invalid ones if any..

XP box is wired, Vista machine is wireless. I haven't tried to ping the XP box from the Vista machine, but I'll try.

Windows 7 laptop is wireless. But... I can access my Vista laptop from my XP box, so I assume it's pinging correctly. Router is a Buffalo N Router, MAC filtering disabled. Firewalls are all disabled, even on the router.

How do I ping to see the ARP table? All I'm doing is PING 192.168.11.5 and getting destination not reachable errors.

  On 17/05/2010 at 16:07, BudMan said:

Is the XP box wireless or wired? What about the vista machine - is it wired or wireless? Can you ping the xp box from the vista machine?

Wireless to wireless could be security feature on your router called Isolation mode that prevents wireless clients from talking to each other.

Lets get your pinging working first so we are sure you have connectivity -- then will worry about file sharing access.

So lets understand your clients -- which one are wired, which ones are wireless.. etc.. For troubleshooting I would suggest you put everything on the wire.. Once that works then you can move a client to wireless. Is your router using any sort of mac filtering? Does it support lan to lan firewall rules? What model of wireless router do you have?

BTW -- same workgroup has NOTHING do with with accessing file shares either.. Sure it can make it easy and faster for browsing to correctly populate -- but is meaningless when looking to ping or share files..

If you can not ping, you either have a firewall issue - or you got some other networking issue going on -- which if the case your never going to get file sharing to work.. So I would suggest you get ping working first.

When you try to ping your xp box, you say you get not reachable vs time out.. So I would assume your not finding the mac of the xp box.

From a command line on your xp box -- do an ipconfig /all -- it will list the mac address for its interfaces - be it wired or wireless..

Now on your win 7 machine - after you try and ping look at your arp table - you should see the xp machines mac address listed, even if there was some firewall on the xp machine preventing ping - you should still get the mac.. if its all zeros for the mac, then you got a issue that is not related to LLTD or workgroup that is for sure.

You could try setting a static arp table entry for the xp box ip on the win 7 box -- can you ping it then?

you can view your arp table on win 7 with arp -a -v will show you all the entries in your table even the invalid ones if any..

example

on your win 7 box - I pinged a client that I know exists the .101 address, then one that does not the .44 address

***

C:\>ping 192.168.1.101

Pinging 192.168.1.101 with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.1.44

Pinging 192.168.1.44 with 32 bytes of data:

Reply from 192.168.1.100: Destination host unreachable.

Reply from 192.168.1.100: Destination host unreachable.

Reply from 192.168.1.100: Destination host unreachable.

Reply from 192.168.1.100: Destination host unreachable.

Ping statistics for 192.168.1.44:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

C:\>arp -a -v

Interface: 127.0.0.1 --- 0x1

Internet Address Physical Address Type

224.0.0.22 static

224.0.0.251 static

224.0.1.24 static

239.255.255.250 static

255.255.255.255 static

Interface: 192.168.1.100 --- 0xb

Internet Address Physical Address Type

192.168.1.4 00-0d-56-f0-f0-09 dynamic

192.168.1.6 00-0c-29-af-0f-54 dynamic

192.168.1.12 00-0c-29-a4-92-ae dynamic

192.168.1.44 00-00-00-00-00-00 invalid

192.168.1.50 00-15-99-21-1c-a0 dynamic

192.168.1.97 00-1c-c3-71-6f-d9 dynamic

192.168.1.98 00-1c-c3-71-72-61 dynamic

192.168.1.99 00-06-dc-43-ad-78 dynamic

192.168.1.101 00-13-20-14-b0-34 dynamic

192.168.1.201 00-22-5f-90-a3-a2 dynamic

192.168.1.202 00-23-14-61-2a-b0 dynamic

192.168.1.203 00-0c-29-01-96-80 dynamic

192.168.1.205 00-1f-e1-52-cd-4e dynamic

192.168.1.207 08-00-27-55-88-37 dynamic

192.168.1.252 00-13-10-fe-84-08 dynamic

192.168.1.253 00-50-04-d8-e8-be dynamic

192.168.1.255 ff-ff-ff-ff-ff-ff static

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

224.0.0.251 01-00-5e-00-00-fb static

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

224.0.1.24 01-00-5e-00-01-18 static

255.255.255.255 ff-ff-ff-ff-ff-ff static

***

Notice how I got an invalid and all zeros for the mac of the .44 address -- that because it does not exist and why you get host not reachable vs just a timeout, where the client knows the mac - but it does not answer -- firewall for example.

You can set a static arp table entry for the mac of the client if you want to see if that resolves your issues -- for some reason just having a issue with arping for the mac? This xp box is working for internet access I assume? You sure you just not on some other wireless network?? That 192.168.11.x is an uncommon private network - most routers default to 192.168.0 or 192.168.1 -- I am guess you changed your router to the .11 segment? Just uncommon is all -- what is the model number of your router btw, a buffalo N does not tell me which specific model ;)

You can set a static arp table entry with from an elevated command prompt, ie admin prompt.

C:\>arp -s 192.168.1.44 00-13-20-14-b0-34

C:\>arp -a

Interface: 192.168.1.100 --- 0xb

Internet Address Physical Address Type

192.168.1.4 00-0d-56-f0-f0-09 dynamic

192.168.1.6 00-0c-29-af-0f-54 dynamic

192.168.1.12 00-0c-29-a4-92-ae dynamic

192.168.1.44 00-13-20-14-b0-34 static

You will need to use the correct mac address and IP for you xp box -- just did this as example of how to do it.. You can get your xp mac from your ipconfig /all on the xp box.

The router is a Buffalo WZR2-G300N. It assigns a 192.168.11.x out of the box, so that's standard for this type of router at least. Definitely different than others I've had.

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Owner>ping 192.168.11.5

Pinging 192.168.11.5 with 32 bytes of data:

Reply from 192.168.11.2: Destination host unreachable.

Reply from 192.168.11.2: Destination host unreachable.

Reply from 192.168.11.2: Destination host unreachable.

Reply from 192.168.11.2: Destination host unreachable.

Ping statistics for 192.168.11.5:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Owner>arp -a -v

Interface: 127.0.0.1 --- 0x1

Internet Address Physical Address Type

224.0.0.22 static

239.255.255.250 static

Interface: 192.168.11.2 --- 0xb

Internet Address Physical Address Type

192.168.11.1 00-16-01-a1-90-49 dynamic

192.168.11.5 00-0f-ea-be-cf-3e invalid

192.168.11.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

Interface: 0.0.0.0 --- 0xffffffff

Internet Address Physical Address Type

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

C:\Users\Owner>

I guess the MAC is invalid. It says Access is Denied when I try to do it from my Win 7 machine, does this need to happen on the XP box?

  On 17/05/2010 at 19:03, BudMan said:

example

on your win 7 box - I pinged a client that I know exists the .101 address, then one that does not the .44 address

***

C:\>ping 192.168.1.101

Pinging 192.168.1.101 with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.1.44

Pinging 192.168.1.44 with 32 bytes of data:

Reply from 192.168.1.100: Destination host unreachable.

Reply from 192.168.1.100: Destination host unreachable.

Reply from 192.168.1.100: Destination host unreachable.

Reply from 192.168.1.100: Destination host unreachable.

Ping statistics for 192.168.1.44:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

C:\>arp -a -v

Interface: 127.0.0.1 --- 0x1

Internet Address Physical Address Type

224.0.0.22 static

224.0.0.251 static

224.0.1.24 static

239.255.255.250 static

255.255.255.255 static

Interface: 192.168.1.100 --- 0xb

Internet Address Physical Address Type

192.168.1.4 00-0d-56-f0-f0-09 dynamic

192.168.1.6 00-0c-29-af-0f-54 dynamic

192.168.1.12 00-0c-29-a4-92-ae dynamic

192.168.1.44 00-00-00-00-00-00 invalid

192.168.1.50 00-15-99-21-1c-a0 dynamic

192.168.1.97 00-1c-c3-71-6f-d9 dynamic

192.168.1.98 00-1c-c3-71-72-61 dynamic

192.168.1.99 00-06-dc-43-ad-78 dynamic

192.168.1.101 00-13-20-14-b0-34 dynamic

192.168.1.201 00-22-5f-90-a3-a2 dynamic

192.168.1.202 00-23-14-61-2a-b0 dynamic

192.168.1.203 00-0c-29-01-96-80 dynamic

192.168.1.205 00-1f-e1-52-cd-4e dynamic

192.168.1.207 08-00-27-55-88-37 dynamic

192.168.1.252 00-13-10-fe-84-08 dynamic

192.168.1.253 00-50-04-d8-e8-be dynamic

192.168.1.255 ff-ff-ff-ff-ff-ff static

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

224.0.0.251 01-00-5e-00-00-fb static

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

224.0.1.24 01-00-5e-00-01-18 static

255.255.255.255 ff-ff-ff-ff-ff-ff static

***

Notice how I got an invalid and all zeros for the mac of the .44 address -- that because it does not exist and why you get host not reachable vs just a timeout, where the client knows the mac - but it does not answer -- firewall for example.

You can set a static arp table entry for the mac of the client if you want to see if that resolves your issues -- for some reason just having a issue with arping for the mac? This xp box is working for internet access I assume? You sure you just not on some other wireless network?? That 192.168.11.x is an uncommon private network - most routers default to 192.168.0 or 192.168.1 -- I am guess you changed your router to the .11 segment? Just uncommon is all -- what is the model number of your router btw, a buffalo N does not tell me which specific model ;)

You can set a static arp table entry with from an elevated command prompt, ie admin prompt.

C:\>arp -s 192.168.1.44 00-13-20-14-b0-34

C:\>arp -a

Interface: 192.168.1.100 --- 0xb

Internet Address Physical Address Type

192.168.1.4 00-0d-56-f0-f0-09 dynamic

192.168.1.6 00-0c-29-af-0f-54 dynamic

192.168.1.12 00-0c-29-a4-92-ae dynamic

192.168.1.44 00-13-20-14-b0-34 static

You will need to use the correct mac address and IP for you xp box -- just did this as example of how to do it.. You can get your xp mac from your ipconfig /all on the xp box.

Alright, final update before I need some suggestions.

I can't ping the Win7 laptop's IP from the XP box, or vice versa. I can if I connect via a wired connection from the Win7 computer.

This leads me to either... the router doesn't support something with Windows 7 or the wireless card is messed up somehow with this router.

I'm leaning toward router since I can't ping from the XP box to the Win7 box either. But.. can't pinpoint the problem. Thought it was an IPv6 problem, but I disabled it all and still didn't work. I can wirelessly access Vista PC's, so I don't know what the deal is.

When you say wireless access the vista PC -- is it wireless as well when you access it or wired?

Your saying it works when wired. Was that mac you listed the correct mac or not? What wireless security are you using? Did you use the routers pushbutton setup for it AOSS I think buffalo calls it -- or did you set it up yourself?? Try going with no encryption for a test.

And again you have not mentioned -- so I will assume it works?? But when wireless you can access the internet just fine from these devices?

The Vista laptop is wireless, not wired. I can access the Vista laptop over the network with my Win7 laptop, which is also wireless.

When I wired the Win7 laptop, I forgot to check the MAC. I'll get back to you on that. Wireless Security is WEP. I did not use the AOSS, I set it up myself. No encryption as in no WEP, etc?

Yes, I can access the Internet on my Win7 machine perfectly as well as all the other PCs.

  On 18/05/2010 at 13:19, BudMan said:

When you say wireless access the vista PC -- is it wireless as well when you access it or wired?

Your saying it works when wired. Was that mac you listed the correct mac or not? What wireless security are you using? Did you use the routers pushbutton setup for it AOSS I think buffalo calls it -- or did you set it up yourself?? Try going with no encryption for a test.

And again you have not mentioned -- so I will assume it works?? But when wireless you can access the internet just fine from these devices?

yeah try turning of the security and see if it works then. Or try WPA or better yet WPA2 -- WEP is no longer a valid way to secure your wireless, it can be hacked in minutes by anyone that has 2 brain cells to rub together and knows how to use google.

If you internet is working then the wireless security should not be an issue -- but you takes 2 seconds to check.. I have seen some weird things with in the past.. Had a friend one time that could only access google if using WPA tkip, WEP worked, wpa2 with aes work -- but tkip just would not work from this one machine for any site other than googles.. Strangest thing I had ever seen ;)

As a test -- just turn off the encryption all together, then clear you arp caches and make sure you can ping.. If you can ping - then try file sharing. If works with no encryption -- then atleast we have more info to work with.. But again WEP is outdated and pretty much pointless unless you have hardware that does not support wpa??

If I recall there are issues with WEP and Draft-N, if you are running N wireless network Im quite sure it supports WPA and pretty sure WPA2 -- there should be no reason in the world your running WEP.

edit: trying to dig up the details of N and WEP -- here is best I could find from a quick look

--

http://www.intel.com/support/wireless/wlan/4965agn/sb/cs-025643.htm

Symptom(s):

Client device's Wi-Fi data rate will not exceed 54 Mbps when Wired Equivalent Privacy (WEP) or Temporal Key Integrity Protocol (TKIP) encryption is configured.

Cause:

The IEEE* 802.11n Draft prohibits using High Throughput with WEP or TKIP as the unicast cipher. If you use these encryption methods (e.g. WEP, WPA-TKIP), your data rate will drop to 54 Mbps. Newer Intel® wireless adapter client drivers connect using a legacy IEEE 802.11g connection rather than failing to connect altogether, which complies with the IEEE 802.11n draft.

--

So if you have a N router -- I for the life of me can not figure out why you would be running WEP?

Edited by BudMan

I have windows 7 on both of my computers. One is wired connection and another is wireless connection. I simply share one computer and can access shared folder from other computer. My living room computer is connected to 52 inch HDTV and I watch movies on that computer. Movies downloaded and shared on one computer works excellently on another computer. Setup is very easy. I think Windows 7 is one of easiest OS for network. It is simple and easy with no fussing around. You can install windows 7 on all your computers then you will not have any problem with networking. Its just alternate method when all else fail.

  • 1 month later...

did you ever fix this problem?

I have a similar issue. I have a wzr2-g300n acting as wifi router, and a linksys acting as adsl modem in bridged mode.

I have recently got a windows7 machine and am having some troubles.

It is connected by wifi to the wzr2-g300n and it can see the internet fine, web browsing is ok. It can also see (ping) all the other wireless devices on the network.

The problem is that it will not ping the desktop machine that is wired into the wzr2-g300n. A packet capture with wireshark shows the arp packets going out of the windows7 box but no replies come back, hence the destination unreachable message. Interestingly though, if i do a packet capture on the desktop, i can see the incoming arp request and the reply goes out less than a millisecond later, the arp reply just seems to get lost in the wzr2-g300n

Any thoughts, .I have disabled firewalls etc but this is a pretty fundamental networking issue. why would windows7 or the wzr2-g300n silently drop arp replies?

So your saying you can talk to wireless devices but not wired ones.

Quick guess would seem like a security feature of your wireless router, don't have time at the moment - but will have to look up the features of that router. kind of like AP isolation mode where you prevent wireless clients from talking to each other.

What you describe would to me be a guest wireless network - allow access to the internet, but not any wired hosts. This is common new feature that everyone wants -- you let your friends over and they can use your internet, but you don't have to worry about them access your shares or infecting your machines with a worm.

This is a common practice in most any work network, you allow access to internet - but not your actual network.

I thought that, but my win vista laptop, ubuntu laptop and xbox360 all connect wirelessly and can talk to the pc that is connected wired. The windows 7 laptop is the only one that is blocked from accessing the wired pc. Its a really strange problem and i cant work it out

Question have you tried setting a static arp entry for your pc on your wireless client, and vice versa>

I find it unlikely that a capture would not show the reply to the arp, if your saying the capture on the pc shows the reply -- that would mean the router is not sending it on, if your not seeing it on the capture on the wireless -- that would say to me its not getting there, not that the client dropped it.. Even if the client was blocking or not paying attention to it - it should still show up in the capture.

Do you have any mac filtering setup on the wireless router? Your not cloning the PCs mac on the router are you?

So when you look at the arp tables your not seeing the other device in the tables of each device - or do they show wrong ones? They show all 0's?

So your saying your win7 box can not see any wired devices at all? You say you have vista and ubuntu machine -- if you wire them, the win7 can not see them either?

I tried to set static arp entry on win7 machine but the arp command seems broken even when run as admin. get some access denied message.

Plugging my ubuntu laptop in wired it has the same symptoms, lost arp messages when trying to ping it from the win7 machine. Interestingly, and i didnt notice this before, when i ping the win7 machine from the wired ubuntu laptop, i see an arp reply from the win7 box with the correct mac, and the icmp ping packets go out on the wire. From the win7 packet capture, i see an arp request and reply and then silence, the icmp ping packets never arrive.

If I ping the ubuntu laptop from win7 then i have the same symptom as before, arp request out, seen on ubuntu and replied to, but the reply never makes it to the win7 machine.

All i can conclude is that the router has some strange bug that stops this windows7 machine communicating between wired and wireless networks.

There is no mac filtering set up on the router and all mac addresses are unique, the only thing i notice is that the win7 one has a mac beginning f0:xxxx wheras all the others are 00:xxxx

I have tried changing the mac address but it seems this feature is also broken in the win7 driver and my setting is ignored.

I doubt you arp command is broken.. Lets see exactly what command your putting in. And yes the cmd prompt will have to be an elevated one.

Well if your ping packets never make it to the win7 machine and your saying your wired is showing the correct mac for that IP -- what does that have to do with the win 7 machine? Sounds more like router issue to me not putting sending the icmp on the wireless. If you saying your seeing the arp and the reply, and your wired devices has the correct mac for the wireless box -- then how can it be something wrong with the wireless machine?? Your sniffing the traffic -- you would see the packets if they were there, be it your machine wanted to process them or not.

As to the mac starting with f0? What are the next 2 and can tell you what the maker of the card is all.. http://www.coffer.com/mac_find/

F0:24:08 TalarisSwe # Talaris (Sweden) AB

F0:26:4C DrSigrist # Dr. Sigrist AG

F0:2F:D8 Bi2-Vision

F0:43:35 DvnShangha # DVN(Shanghai)Ltd.

F0:4B:F2 JtechCommu # JTECH Communications, Inc.

F0:4D:A2 Dell # Dell Inc.

F0:62:81 ProcurveNe # ProCurve Networking by HP

F0:65:DD PrimaxElec # Primax Electronics Ltd.

F0:68:53 Integrated # Integrated Corporation

F0:77:D0 Xcellen

F0:7B:CB HonHaiPrec # Hon Hai Precision Ind. Co.,Ltd.

F0:7D:68 D-Link # D-Link Corporation

F0:9C:BB Raonthink # RaonThink Inc.

F0:AD:4E Globalscal # Globalscale Technologies, Inc.

F0:B6:EB PoslabTech # Poslab Technology Co., Ltd.

F0:BC:C8 MaxidPty # MaxID (Pty) Ltd

F0:BD:F1 Sipod # Sipod Inc.

F0:C2:4C ZhejiangFe # Zhejiang FeiYue Digital Technology Co., Ltd

F0:D7:67 AxemaPassa # Axema Passagekontroll AB

F0:DE:71 ShanghaiEd # Shanghai EDO Technologies Co.,Ltd.

F0:DE:F1 WistronInf # Wistron InfoComm (Kunshan)Co

F0:E5:C3 Draegerwer # Draegerwerk AG &amp; Co. KG aA

F0:EC:39 Essec

F0:ED:1E BilkonBilg # Bilkon Bilgisayar Kontrollu Cih. Im.Ltd.

F0:F8:42 Keebox # KEEBOX, Inc.

F0:F9:F7 Ies&Amp; # IES GmbH & Co. KG

Maybe your router has an issue with the mac of the win 7 wireless card?? Here is thread where the person says their router would not allow him to enter the F0: mac into his routers allowed mac address list, etc.

http://forum.notebookreview.com/networking-wireless/470838-netgear-dgn2000-refusing-laptops-mac.html

What wireless card are you using?

It is a broadcom 43225 chipset, mac is : F0:7B:CB HonHaiPrec

I did try to change the mac from the windows driver settings but it just stays the same on the wire no matter what i type in the box.

I did try it with an ubuntu live cd (10.04) to check the card in a different os, but sadly this chipset doesn't seem to be supported.

the arp command i used in win7 that i was having trouble was

arp -s 192.168.1.125 xx-xx-xx-xx-xx-xx

just an access denied message from a root shell

What machine were you doing that on? the wired machine correct - and xx-xx is the wireless machine.

post-14624-1279803427654.jpg

Oh that is Foxconn, what laptop is this -- is it a built in wireless, or a dongle?

I have found the ubuntu driver for the wifi card on the laptop and installed it from the live cd. It is one of the restricted closed source ones.

Just to prove that the router is doing something funny and it is not windows 7, i tried the same things with ubuntu.

Ubuntu on the win7 laptop can not ping the wired side of the network either, just the same as when running windows 7. It just seems the router or laptop network card is just losing packets when talking to the wired network from wireless side

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

    • No registered users viewing this page.
  • Posts

    • who ever thought this looked good needs to rethink their design credentials.....
    • There's a few here upset Kamala Harris never got the Presidency! lol....
    • Yeah, he identified a whole lot of wasteful spending of US taxpayer money. What's wrong with that? Nothing, unless you had your fingers in the pie of course.
    • How to reduce the annoying Liquid Glass effects on iOS 26 by Aditya Tiwari Apple announced Liquid Glass at WWDC 2025 in all of its glory. It's a new glass-inspired design language from the iPhone-maker making its way to most of its software platforms, including iOS 26, iPadOS 26, macOS 26, tvOS 26, and watchOS 26. Apple markets Liquid Glass as a new translucent material that "behaves like glass in the real world. Its color is informed by surrounding content and intelligently adapts between light and dark environments." The Cupertino giant isn't wrong. The new glass-inspired design does bring a fresh coat of paint and some beautiful visuals to the iPhone and other Apple-made devices. However, as the dust from the mega arrival settles, people are starting to realize the current drawbacks of having too much glass on their device. There have been reports of users, including those at Neowin, experiencing readability issues, background separation issues, and trouble focusing on the content displayed on the screen due to its transparent nature. While these are small nuances on Apple's part that can be fixed without much hassle, it's degrading the initial experience of what the company calls its biggest visual upgrade since iOS 7. That said, there are some workarounds built into iOS 26 that will help you tone down the shortcomings. If you're running the iOS 25 Developer Beta 1 on your supported iPhone model, you can follow these steps to make things a little better: Go to the Settings app on your iPhone. Scroll down and tap on Accessibility > Display & Text Size. Next, you'll find two toggle options: Reduce Transparency and Increase Contrast. When you enable the Reduce Transparency toggle button, iOS 26 can "improve contrast by reducing transparency and blurs on some backgrounds to increase legibility." The other toggle, Increase Contrast, does what its name suggests. It can "increase color contrast between app foreground and background colors." Enabling each of these toggle buttons individually or simultaneously will have different effects on your iPhone's user interface. Control Center is being criticized for the extra transparency, making the UI look cluttered and difficult to focus. Here, the Reduce Transparency button adds a darker background to make the Control Center UI elements stand out. Liquid Glass transparency issues are also prevalent in the Notification Center and the navigation controls of various apps. In the image above, see how the text of the navigation buttons has become unreadable or hard to focus on with certain backgrounds. It's challenging to determine what can trigger such behavior, as one can have countless color combinations on their device. In the image below, this is how these buttons look when both Reduce Transparency and Increase Contrast are enabled. It's still a hit or miss depending on what colors you are dealing with. Part of the blame also goes to the fact that iOS 26 is still an early beta, and the change doesn't render as intended every time. You can also notice the difference in the look and feel of the Control Center when reduced transparency is turned on. On a side note, you can add the Reduce Transparency and Increase Contrast buttons in the Control Center for quicker access. That said, let's wait to see what changes Apple will implement as it continues to gather feedback through the beta program. Hopefully, the software will become more stable when the first public beta of iOS 26 arrives sometime in July. Interested users can try out the latest iPhone update through the developer beta program, noting that early builds might come with unexpected bugs and issues.
    • Austin residents rally against Tesla's robotaxi launch by Hamid Ganji Tesla's plan to launch its robotaxi service in Austin, Texas, has sparked protests in the city. While the EV maker targets June 22 as the launch date, local residents are raising their voices against the plan due to political disagreements and safety concerns. As reported by CNBC, public safety advocates and political protesters are organizing protests against Tesla's robotaxi launch in Austin. Members of the Dawn Project, Tesla Takedown, and Resist Austin have cited safety issues with Tesla's automated driving systems. Meanwhile, Elon Musk's involvement in Donald Trump's administration and his work in the Department of Government Efficiency (DOGE) has prompted another group of people to join the Austin protests against Tesla. To show Austin citizens the safety problems of Tesla's self-driving system, The Dawn Project brought a Tesla Model Y to the protest, equipped with the company's Full Self-Driving (FSD) software (version 13.2.9). In the demonstration, the Model Y with FSD software reportedly zoomed past a school bus with a stop sign held out and ran over a child-sized mannequin placed in front of the car. The FSD package includes automatic lane-keeping, steering, and parking. It is unclear to what extent this test was conducted under standard conditions or what Tesla's defense is. However, multiple cases of Tesla FSD software malfunction in the past have resulted in collisions or severe accidents, according to data collected by National Highway Traffic Safety Administration. Interestingly, The Dawn Project CEO Dan O'Dowd is the CEO of another company that sells embedded safety and security solutions to carmakers like Ford and Toyota. It remains to be seen whether Tesla could launch a robotaxi service in Austin despite the residents' protests. Earlier this week, Elon Musk demonstrated the new version of Tesla's FSD software in a post on X. Musk's decisions on DOGE fuel public backlash against Tesla. While Musk left the Trump administration after a beef with the president, he's still a target of public criticism, which directly imapcts Tesla. As a result, the slow sales have even caused Tesla to sell its Cybertruck with 0 percent APR to boost sales.
  • Recent Achievements

    • One Month Later
      greege earned a badge
      One Month Later
    • Week One Done
      greege earned a badge
      Week One Done
    • Week One Done
      LagFighterZ earned a badge
      Week One Done
    • First Post
      ThatGuyOnline earned a badge
      First Post
    • One Month Later
      5i3zi1 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      547
    2. 2
      ATLien_0
      230
    3. 3
      +FloatingFatMan
      166
    4. 4
      Michael Scrip
      119
    5. 5
      +Edouard
      91
  • Tell a friend

    Love Neowin? Tell a friend!