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


Recommended Posts

FIXED it..... Yay

With Windows7 you CANNOT change the MAC address to one without bit 2 of the first byte set. ie it must be x2-xx- or any other number with bit 2 set. bit 2 of the first byte denotes a "locally administered MAC address"

I changed the windows7 MAC to 02-xx-xx-xx-xx-xx where the xx numbers were the same as the original MAC.

It seems that the Buffalo WZR2-G300N has a bug where it cannot cope with MAC addresses beginning f0-xx and will not forward packets between wired and wireless networks.

Also the Broadcom 43225 wireless chipset cant seem to cope on anything other than channel 1. I get random dropped connections on other channels. other machines are rock solid.

Im just glad it is now working and I can get on with other things.

Thanks for your help.

Where did you dig this info up?

"ie it must be x2-xx- or any other number with bit 2 set. bit 2 of the first byte denotes a "locally administered MAC address"

Would love to see the source article on this -- is a MS article?

Glad you got it sorted, yeah thats a strange bug to be sure.. Is buffalo aware of it?

The wikipedia page shows the structure of a mac address, special bits etc...

Wikipedia MAC Address page

I just came across the windows 7 "feature/limitation" in another forum, cant remember which one now, but i found quite a few people complaining that they cant change their mac address in windows 7. This is apparently particularly annoying when they must "spoof" a particular mac address to make their pc talk to their cable modems so I read. The most annoying thing for me is that it doesnt tell you that you have entered an invalid address, it just silently ignores the value you entered and the change MAC address function appears broken.

I havent told buffalo, but that is not to say they dont know about it, this is an older router now, not sure they still make them or would care about it. My experience of technical support for routers was soured by many a conversation with belkin's support a little while back. They couldnt seem to understand that power cycling my router every couple of days to bring the internet back up was not an acceptable solution. Never did get it sorted and will never buy a belkin again.

I well aware of the structure of a mac address ;) I was curious where you cam across that specific w7 limitation spelled out.

Since its clearly not a limitation on wired interfaces.

edit: hit the wrong button

post-14624-12800000516312.jpg

btw: just in case someone is pretty dense, I changed my mac to that -- what would be the odds you would see AABBCC for the last 3?? ;)

Now I also recall some threads here about users not being able to change their wireless mac, but If I recall it was only on 64bit.. And at the time did not have a win 7 x64bit wireless to test with -- now I have my wifes laptop, so going to have to go test it. But if this is clearly a limitation set by MS you would think it would be documented somewhere ;)

Edited by BudMan

Well, I shouldnt have said that with such authority. Its definately true that with my HP laptop running Windows 7 64-bit and a Broadcom 43225 WIFI adaptor that you cant change the wifi mac to anything else unless you set the "locally administered" bit. I just read in other forums that other people were having the same issue with windows 7. Maybe its the 3rd party supplied driver or maybe its windows, who knows, but its a bit of a pain when it just silently ignores your setting.

  On 24/07/2010 at 19:32, BudMan said:

I well aware of the structure of a mac address ;) I was curious where you cam across that specific w7 limitation spelled out.

Since its clearly not a limitation on wired interfaces.

edit: hit the wrong button

post-14624-12800000516312.jpg

btw: just in case someone is pretty dense, I changed my mac to that -- what would be the odds you would see AABBCC for the last 3?? ;)

Now I also recall some threads here about users not being able to change their wireless mac, but If I recall it was only on 64bit.. And at the time did not have a win 7 x64bit wireless to test with -- now I have my wifes laptop, so going to have to go test it. But if this is clearly a limitation set by MS you would think it would be documented somewhere ;)

  • 5 months later...

Hello! I am having exactly this problem between wired and wireless boxes on my buffalo crappy wzr2-g300n!! Yours is the first post that explains the bug that I found on the internet.

My win7x64 box has a MAC beginngin with E0-xx...and it won't forward packets between wired and wireless either.

Could you please explain in a bit more detail how you fixed this problem? I have been researching this for 10 days!! Thanks so much!

  On 23/07/2010 at 18:51, jaialrai said:

FIXED it..... Yay

With Windows7 you CANNOT change the MAC address to one without bit 2 of the first byte set. ie it must be x2-xx- or any other number with bit 2 set. bit 2 of the first byte denotes a "locally administered MAC address"

I changed the windows7 MAC to 02-xx-xx-xx-xx-xx where the xx numbers were the same as the original MAC.

It seems that the Buffalo WZR2-G300N has a bug where it cannot cope with MAC addresses beginning f0-xx and will not forward packets between wired and wireless networks.

Also the Broadcom 43225 wireless chipset cant seem to cope on anything other than channel 1. I get random dropped connections on other channels. other machines are rock solid.

Im just glad it is now working and I can get on with other things.

Thanks for your help.

He changed the mac of the interface that started with f0 to start with 02. Do you not know how to change the mac? So your saying the buffalo will not pass traffic if the mac starts with E0 either? Seems pretty freaking odd to block out all these makers of networking devices.

E0-05-C5 (hex) TP-LINK Technologies Co.,Ltd.

E005C5 (base 16) TP-LINK Technologies Co.,Ltd.

Building 7, Second Part, Honghualing Industrial Zone

Xili town, Nanshan,

Shenzhen Guangdong 518000

CHINA

E0-0C-7F (hex) Nintendo Co., Ltd.

E00C7F (base 16) Nintendo Co., Ltd.

11-1 HOKOTATE-CHO

KAMITOBA, MINAMI-KU

KYOTO 601-8501

JAPAN

Just these two listings look like a MAJOR issue if you ask me.. TP-link makes a LOT of networking gear, and well Nintendo so your saying that buffalo will not pass traffic for macs starting with E0?? So you can not use your WII, etc ?

By the way, I figured out how to change my MAC on my Marvell network adapter. I used your idea of 02-xx-xx-xx... where I used the old mac and just changed the first two digits to 02. However, (1) my problem did not go away, and (2) now my buffalo says there are two wired MAC controllers connecting to the router (one that is the new MAC I created and one that I've never seen before).

Thanks.

  On 31/12/2010 at 16:59, BtoA said:

Hello! I am having exactly this problem between wired and wireless boxes on my buffalo crappy wzr2-g300n!! Yours is the first post that explains the bug that I found on the internet.

My win7x64 box has a MAC beginngin with E0-xx...and it won't forward packets between wired and wireless either.

Could you please explain in a bit more detail how you fixed this problem? I have been researching this for 10 days!! Thanks so much!

Seems to be the case!

I'm trying to get iTunes to stream music to an Airport Express box connected to speakers. My win7x64 box sees the AE...but will not stream music to it. I had apple on the line...they had no clue. So it looks like it's a buffalo issue. what a piece of garbage if this is the case. Just as described here, my laptops can stream to the AE speaker but NOT the wired win7 box.

I did just change the MAC to 02-xx as described, but still no joy. Even restarted the router.

  On 31/12/2010 at 17:17, BudMan said:

He changed the mac of the interface that started with f0 to start with 02. Do you not know how to change the mac? So your saying the buffalo will not pass traffic if the mac starts with E0 either? Seems pretty freaking odd to block out all these makers of networking devices.

E0-05-C5 (hex) TP-LINK Technologies Co.,Ltd.

E005C5 (base 16) TP-LINK Technologies Co.,Ltd.

Building 7, Second Part, Honghualing Industrial Zone

Xili town, Nanshan,

Shenzhen Guangdong 518000

CHINA

E0-0C-7F (hex) Nintendo Co., Ltd.

E00C7F (base 16) Nintendo Co., Ltd.

11-1 HOKOTATE-CHO

KAMITOBA, MINAMI-KU

KYOTO 601-8501

JAPAN

Just these two listings look like a MAJOR issue if you ask me.. TP-link makes a LOT of networking gear, and well Nintendo so your saying that buffalo will not pass traffic for macs starting with E0?? So you can not use your WII, etc ?

And what is the IP of the AE speaker?

Can you ping in from the w7 box?

What does arp -a show for the mac of the AE, can you see the mac?

If you believe its the router not passing macs that start with E0, then you should be able to get your laptop to stop working by changing your MAC to start with E0..

But since you stated you changed your mac to not be E0, or F0 like the OP had an issue with it seems that its not a mac based issue but something else.

I would suggest standard troubleshooting.. You say your w7 can see this AE.. Ok if you can ping the IP, then its clearly NOTHING wrong with your router passing traffic based up on the mac address of your device and something else is the problem.

good points!

I cannot ping the AE (at 192.168.11.3) from my win7x64 box.

arp -a for the AE returns "No ARP entries found."

with just arp -a, the AE mac does not show up.

meanwhile, my win7 "sees" the AE when I run itunes or airport utility... that is, the software knows the AE exists... but it won't connect. How strange that itunes knows the AE exists, but I can't ping the AE. From my router config page, I can clearly see the AE MAC and its dynamic IP address.

  On 31/12/2010 at 17:49, BudMan said:

And what is the IP of the AE speaker?

Can you ping in from the w7 box?

What does arp -a show for the mac of the AE, can you see the mac?

If you believe its the router not passing macs that start with E0, then you should be able to get your laptop to stop working by changing your MAC to start with E0..

But since you stated you changed your mac to not be E0, or F0 like the OP had an issue with it seems that its not a mac based issue but something else.

I would suggest standard troubleshooting.. You say your w7 can see this AE.. Ok if you can ping the IP, then its clearly NOTHING wrong with your router passing traffic based up on the mac address of your device and something else is the problem.

Try creating a static arp entry for your AE.

Can you ping it now? Your never going to be able to talk to it with out a mac address.

You can get its mac from your router, or better yet from a machine that can talk to it.. Ie your laptop -- look at its arp table, now create a static for that mac and IP on your w7 box.

edit: btw

"my laptops can stream to the AE speaker but NOT the wired win7 box."

Are you laptop wireless or wired?? I looked for the manual for that router - but the one I found was a POS, no details of features, etc. But many wireless routers can allow you to block traffic between wireless and wired, ie some my call it guest internet, etc.

going to look to see if I can find a better manual for that router.

Thanks!

AE: for whatever reason, I know run arp -a, and I can see the MAC of the AE. dynamically assigned to 192.168.11.3 but... when I try to ping that IP, I get no reply.

The laptop is connected wirelessly to my network on the buffalo router. It CAN ping the AE at 192.168.11.3, even though its arp -a does not show the AE's MAC or IP.

I have a manual for the router. It is so old, though, that it does not offer a "feature" of blocking wireless and wired connections. I think it's really a bug. The question is how to get around it. Changing the MAC just doesn't do it. I guess I'll either have to get a usb adapter to connect my win7 box wirelessly to the router... or... just buy a new router. The guy who started this thread says he got things to work by changing his MAC to 02-xx but that just didn't work in my case. bummer.

I really appreciate your help - especially during the holidays...

  On 01/01/2011 at 16:21, BudMan said:

Try creating a static arp entry for your AE.

Can you ping it now? Your never going to be able to talk to it with out a mac address.

You can get its mac from your router, or better yet from a machine that can talk to it.. Ie your laptop -- look at its arp table, now create a static for that mac and IP on your w7 box.

edit: btw

"my laptops can stream to the AE speaker but NOT the wired win7 box."

Are you laptop wireless or wired?? I looked for the manual for that router - but the one I found was a POS, no details of features, etc. But many wireless routers can allow you to block traffic between wireless and wired, ie some my call it guest internet, etc.

going to look to see if I can find a better manual for that router.

"It CAN ping the AE at 192.168.11.3, even though its arp -a does not show the AE's MAC or IP."

IMPOSSIBLE Completely IMPOSSIBLE!!!

Unless you are different networks???

Its impossible for you to ping something on your local segment without knowing is MAC, now if the IP your trying to ping is not on your network segment, then you will send the traffic to your gateway.

Please post the outputs of your w7 ipconfig all and your laptop ipconfig /all

And before you get all worried about posting info like this.. as long as the IPs are private, 10.x.x.x, 192.168.x.x 172.16-31.x.x they in no way what so ever point to you..

So for example this is my desktop ipconfig /all

C:\Windows\System32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : quad-w7

Primary Dns Suffix . . . . . . . : local.lan

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : local.lan

Ethernet adapter gig:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller

Physical Address. . . . . . . . . : 00-21-9B-03-AC-A7

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.253

DNS Servers . . . . . . . . . . . : 192.168.1.253

NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Windows\System32>

Now -- if you look at your arp table before you ping, and you don't see anything that does not mean anything.. Do it right after.. So for example

Notice no .6 in there at first, But I can ping it -- but notice right after I ping it.

C:\Windows\System32>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.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.253 00-09-5b-e2-cc-db 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.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

C:\Windows\System32>ping 192.168.1.6

Pinging 192.168.1.6 with 32 bytes of data:

Reply from 192.168.1.6: bytes=32 time=1ms TTL=64

Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.6:

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

Approximate round trip times in milli-seconds:

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

C:\Windows\System32>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.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.253 00-09-5b-e2-cc-db 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.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

C:\Windows\System32>

So this is amazing.....

I noticed that my win7 desktop workgroup was different from my vista laptop workgroup. I changed the desktop (connected via ethernet cable) workgroup to match the laptop workgroup. I restarted the win7 box, and magic! For the FIRST time, I could ping from my desktop to the AE speakers' IP address. Everything worked instantly!! The iTunes on the desktop was controlled by an ipad and streamed music to the AE speakers.

BUT!!!!! BUT!!!! I walked away from the PC for a few hours... and came back... I tested the connection by ping'ing the AE speakers. Dead. the iPad remote would no longer connect. Dead. the Airport Utility gave me the same -6753 error as before.

It all worked perfectly!! for a brief moment.

So what did I do between when things were worked and when they were not? Nothing.

I tried to change the workgroup back to the old name. restarted. changed the workgroup back to the same workgroup name as the laptop. dead. I can't seem to bring it back.

BTW, you are exactly right about the arp -a list. AFTER I run Airport Utility, which finds the AE, I type arp -a, and I can see the AE's IP and MAC. However, if I try to ping the AE, I get request timed out.

C:\>arp -a

Interface: 192.168.11.4 --- 0xd

Internet Address Physical Address Type

192.168.11.1 00-16-xx-xx-xx-xx dynamic

192.168.11.3 78-ca-xx-xx-xx-xx dynamic <----- AE

192.168.11.5 00-1c-xx-xx-xx-xx dynamic

192.168.11.7 00-0e-xx-xx-xx-xx dynamic

192.168.11.253 00-80-xx-xx-xx-xx dynamic

192.168.11.255 xx-xx-xx-xx-xx-xx static

224.0.0.22 01-00-xx-xx-xx-xx static

224.0.0.251 01-00-xx-xx-xx-xx static

224.0.0.252 01-00-xx-xx-xx-xx static

224.0.0.253 01-00-xx-xx-xx-xx static

239.255.255.250 01-00-xx-xx-xx-xx static

255.255.255.255 xx-xx-xx-xx-xx-xx static

C:\>ping 192.168.11.3

Pinging 192.168.11.3 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 192.168.11.3:

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

C:\>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : xx

IPv4 Address. . . . . . . . . . . : 192.168.11.4

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.11.1

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter isatap.{x}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter isatap.{x}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 12:

Connection-specific DNS Suffix . :

IPv6 Address. . . . . . . . . . . : x

Link-local IPv6 Address . . . . . : x

Default Gateway . . . . . . . . . : ::

  On 02/01/2011 at 15:18, BudMan said:

"It CAN ping the AE at 192.168.11.3, even though its arp -a does not show the AE's MAC or IP."

IMPOSSIBLE Completely IMPOSSIBLE!!!

Unless you are different networks???

Its impossible for you to ping something on your local segment without knowing is MAC, now if the IP your trying to ping is not on your network segment, then you will send the traffic to your gateway.

Please post the outputs of your w7 ipconfig all and your laptop ipconfig /all

And before you get all worried about posting info like this.. as long as the IPs are private, 10.x.x.x, 192.168.x.x 172.16-31.x.x they in no way what so ever point to you..

So for example this is my desktop ipconfig /all

C:\Windows\System32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : quad-w7

Primary Dns Suffix . . . . . . . : local.lan

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : local.lan

Ethernet adapter gig:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller

Physical Address. . . . . . . . . : 00-21-9B-03-AC-A7

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.253

DNS Servers . . . . . . . . . . . : 192.168.1.253

NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Windows\System32>

Now -- if you look at your arp table before you ping, and you don't see anything that does not mean anything.. Do it right after.. So for example

Notice no .6 in there at first, But I can ping it -- but notice right after I ping it.

C:\Windows\System32>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.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.253 00-09-5b-e2-cc-db 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.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

C:\Windows\System32>ping 192.168.1.6

Pinging 192.168.1.6 with 32 bytes of data:

Reply from 192.168.1.6: bytes=32 time=1ms TTL=64

Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.6:

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

Approximate round trip times in milli-seconds:

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

C:\Windows\System32>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.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.253 00-09-5b-e2-cc-db 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.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

C:\Windows\System32>

^ What :blink:

What does a router bug not forwarding traffic based up mac have to do with XP or W7??

As to what this next users root issue is, I am not sure -- but again find it HIGHLY unlikely its a w7 issue

I share files with XP, linux other devices with w7 - both directions, etc. etc.. never issue one. And to be honest, pretty much every single issue I have with users sharing files is 3rd party firmware, plain and simple PEBKAC or just plain lack of RTFM.

edit:

Lets be clear about something.. what workgroup your machines are in have NOTHING to do with network access - NOTHING!! If your saying it worked after change of workgroup name and reboot.. I would say your having a browsing issue..

Why are you snipping out info??? WTF you think anyone is going to do with a MAC address.. Atleast leave the first 3 numbers so can look up who makes the freaking thing ;)

If you seeing mac and can not ping, then either firewall problem, or wrong mac or like you said router is not forwarding traffic.. Does the mac address match and IP address from the device that is working..

What is the exact device your trying to work with AE speakers?? What is model number of this thing so I can look up how they work.

edit2: What Airport utility?? And what is the FULL error??

edit3: Trying to find your AE speakers, etc.. prob has to do with the Bonjour service as well. Your going to need to give more details if you want help.. But Lets be 100% clear about something.. If you can ping ANYTHING on the wireless side from your w7 with the mac of f0 or E0 or whatever -- then its not a router problem with forwarding packets based upon mac.

When you say your laptop can use the AE speakers -- ok put your laptop on wired side -- does it still work?? Sound more like you go some name resolution issue with either network browsing service or that Bonjour nonsense from apple.

LOL. Think you must be right!

So probably not the workgroup name after all... though that is what I changed just before I had that brief moment when I could ping the AE.

Another experiment: I check arp -a just after restart. NO AE IP / MAC on the list.

I ping'ed the AE's IP address and got timed out.

But....

The AE's IP/MAC appeared when I then checked arp -a:

C:\>arp -a

Interface: 192.168.11.4 --- 0xd

Internet Address Physical Address Type

192.168.11.1 xx-xx-xx-xx-xx-xx dynamic

192.168.11.5 xx-xx-xx-xx-xx-xx dynamic

192.168.11.6 xx-xx-xx-xx-xx-xx dynamic

192.168.11.7 xx-xx-xx-xx-xx-xx dynamic

192.168.11.255 xx-xx-xx-xx-xx-xx static

224.0.0.22 xx-xx-xx-xx-xx-xx static

224.0.0.251 xx-xx-xx-xx-xx-xx static

224.0.0.252 xx-xx-xx-xx-xx-xx static

224.0.0.253 xx-xx-xx-xx-xx-xx static

239.255.255.250 xx-xx-xx-xx-xx-xx static

255.255.255.255 xx-xx-xx-xx-xx-xx static

C:\Users\b>ping 192.168.11.3

Pinging 192.168.11.3 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 192.168.11.3:

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

C:\>arp -a

Interface: 192.168.11.4 --- 0xd

Internet Address Physical Address Type

192.168.11.1 xx-xx-xx-xx-xx-xx dynamic

192.168.11.3 xx-xx-xx-xx-xx-xx dynamic

192.168.11.5 xx-xx-xx-xx-xx-xx dynamic

192.168.11.6 xx-xx-xx-xx-xx-xx dynamic

192.168.11.7 xx-xx-xx-xx-xx-xx dynamic

192.168.11.255 xx-xx-xx-xx-xx-xx static

224.0.0.22 xx-xx-xx-xx-xx-xx static

224.0.0.251 xx-xx-xx-xx-xx-xx static

224.0.0.252 xx-xx-xx-xx-xx-xx static

224.0.0.253 xx-xx-xx-xx-xx-xx static

239.255.255.250 xx-xx-xx-xx-xx-xx static

255.255.255.255 xx-xx-xx-xx-xx-xx static

C:\>

  On 02/01/2011 at 16:03, BudMan said:

^ What :blink:

What does a router bug not forwarding traffic based up mac have to do with XP or W7??

As to what this next users root issue is, I am not sure -- but again find it HIGHLY unlikely its a w7 issue

I share files with XP, linux other devices with w7 - both directions, etc. etc.. never issue one. And to be honest, pretty much every single issue I have with users sharing files is 3rd party firmware, plain and simple PEBKAC or just plain lack of RTFM.

Dude if you want help stopping snipping out the macs.. There is NOTHING I can do with that info, there is NOTHING anyone can do with that info..

your the one saying you think it was a mac related problem with your router not fowarding -- but then you snip them out???

The most anyone can do with the a mac, is lookup what hardware it is from the vendor listing..

as you see I posted my arp -a output, did you see me mark out anything??

Only mac you might be worried about is the radio mac of a Accesspoint -- since there are database where you could look up location based upon than..

ok. sorry for the paranoia. the internet is filled with friends like you....and some foes out there... I only xx'ed out the access point.

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : b-pc

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether

net Controller #2

Physical Address. . . . . . . . . : E0-CB-4E-92-7E-BA

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.11.4(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Monday, 03 January, 2011 12:02:55 AM

Lease Expires . . . . . . . . . . : Wednesday, 05 January, 2011 12:02:54 AM

Default Gateway . . . . . . . . . : 192.168.11.1

DHCP Server . . . . . . . . . . . : 192.168.11.1

DNS Servers . . . . . . . . . . . : 192.168.11.1

NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether

net Controller

Physical Address. . . . . . . . . : E0-CB-4E-92-77-65

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

C:\>arp -a

Interface: 192.168.11.4 --- 0xd

Internet Address Physical Address Type

192.168.11.1 00-16-xx-xx-xx-xx dynamic

192.168.11.3 78-ca-39-46-ed-c9 dynamic

192.168.11.5 00-1c-26-26-54-43 dynamic

192.168.11.6 c8-bc-c8-26-18-6a dynamic

192.168.11.7 00-0e-7f-e9-f1-69 dynamic

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.251 01-00-5e-00-00-fb static

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

224.0.0.253 01-00-5e-00-00-fd static

239.192.152.143 01-00-5e-40-98-8f static

239.255.255.250 01-00-5e-7f-ff-fa static

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

C:\>ping 192.168.11.3

Pinging 192.168.11.3 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 192.168.11.3:

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

C:\>

  On 02/01/2011 at 16:20, BudMan said:

Dude if you want help stopping snipping out the macs.. There is NOTHING I can do with that info, there is NOTHING anyone can do with that info..

your the one saying you think it was a mac related problem with your router not fowarding -- but then you snip them out???

The most anyone can do with the a mac, is lookup what hardware it is from the vendor listing..

as you see I posted my arp -a output, did you see me mark out anything??

Only mac you might be worried about is the radio mac of a Accesspoint -- since there are database where you could look up location based upon than..

Ok this makes no sense

http://www.coffer.com/mac_find/?string=78-ca-39

No matches found for "78-ca-39"

So again what is this exact model number of this device??

And does your laptop that work see the same mac?

Thanks. That device is the apple airportexpress. I looked up apple on that coffer site, and there are no 78-xxxxx mac's listed. odd.

The wireless router is a buffalo wzr2-g300N. I'm almost at the point of bin'ing the thing and starting again with a new router.... Would bother you less!

Thanks for the helping hand.

  On 02/01/2011 at 21:44, BudMan said:

Ok this makes no sense

http://www.coffer.com/mac_find/?string=78-ca-39

No matches found for "78-ca-39"

So again what is this exact model number of this device??

And does your laptop that work see the same mac?

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

    • No registered users viewing this page.