Why doesn't Vista RC1 allow pings to 169.254.1.1? I have a wireless broadband connection and management of the antenna is gate to 169.254.1.1. Problem is, on XP, I can hit this ip thru both MS-DOS and via a browser,and see how it is performing, radio strength of the base station i'm connected to, etc, etc. On Vista RC1 it seems access to this address is not allowed. What gives?

I cannot access 169.254.1.1 either in Vista. It is to the Canopy Wireless. In XP, I can access 169.254.1.1 with the browser, and pings to it works. In Vista, neither works.

Vista SP1 - same problem. I get "Destination network unreachable". My Linksys router can ping it just fine. XP systems can browse to it just fine. What's the problem???

???? I Want to Know Too ???? BobbyRoa wrote: Why doesn't Vista RC1 allow pings to 169.254.1.1? I have a wireless broadband connection and management of the antenna is gate to 169.254.1.1. Problem is, on XP, I can hit this ip thru both MS-DOS and via a browser,and see how it is performing, radio strength of the base station i'm connected to, etc, etc. On Vista RC1 it seems access to this address is not allowed. What gives?

I Need Too Know? BobbyRoa wrote: Why doesn't Vista RC1 allow pings to 169.254.1.1? I have a wireless broadband connection and management of the antenna is gate to 169.254.1.1. Problem is, on XP, I can hit this ip thru both MS-DOS and via a browser,and see how it is performing, radio strength of the base station i'm connected to, etc, etc. On Vista RC1 it seems access to this address is not allowed. What gives?

I work for an ISPthat uses Motorola Canopy exclusively. Because of the issues with Vista not being able to access stuff, we have so far refused to upgrade (we even downgraded 2 Dell laptops to XP at a substantial cost to avoid Vista). However, if you need to ping and it won't work, go to Start->Programs->Accessories and then either in that menu or under System tools there will be the command prompt shortcut. Right click and Run as Administrator. That shoule let you ping as well as use all the Ipconfig*** commands. As for the webpage. There are two main reasons why that page is unnaccessable. 1st one is that the radio can be programmed with any valid IP address. The ISP I work for gives each radio a unique IP on our vpn to allow for easy access via a one click system our helpdesk uses. That also prevents consumers from accessing the radio. The 2nd one is that with a public IP you may not be on the right Subnet to access the radio. The default is IP: 169.254.1.1 Subnet: 255.255.255.0 If you don't have a router, try setting your computers IP to 169.254.1.99 and Subnet to 255.255.255.0 and your DNS to 10.10.2.10 and see if that works. If you use a router, you may need to bypass it or set the above information in it and try connecting through it. Remember to write down any Static IP info you have saved before changing it, or you may end up spending a while on the phone with your ISP trying to get it set again before you can access the internet. If someone tries all that and it still doesn't work, repost here and I'll try and help you some more.

When I first noticed the problem, I tried bypassing my router with my Vista computer. At that time, it still could not access the Canopy status page, or ping 169.254.1.1.I last tested the bypass in May 2008, then just tested it again a few days ago. Something has changed, because now my Vista computer bypassing the router can access the Canopy status page, and pings to 169.254.1.1 work. When connected to the router, though, it doesn't work.At this time, it appears that my D-Link wired router doesn't like Vista, but does like XP. This doesn't make much sense to me, since I figure that it shouldn't matter what kind of computer or operating system makes a request to a router.When the Vista is connected to the router, pings to 169.254.1.1 now get a response of:"Reply from 192.168.0.100: Destination host unreachable." 192.168.0.100 is the IP that the router has assigned to my Vista computer. Obviously the router is interfering, but I don't know why.Previously, the same ping with the same router & computer would not get any response.I suppose I could ask D-Link what's going on with this, but I doubt I would get any good answers from them. I never got any response from Motorola, and my ISP has not been very helpful.

It's not neccessarily the router that has the problem. Vista added a whole new set of security measures that may be the problem. However, try pinging every point you can from your computer's IP to an external site such as Microsoft.com or google.com. Do "tracert www.microsoft.com" in a command prompt if you need the IPs to ping. Also, routers (more accurately called a "Residential Gateway") are prone to blocking such things. Check and see that there isn't a setting in the router that's discarding pings. Generally though it will only discard pings from the WAN, or outside your Local network. As for why it works now and didn't before, probably an update from Microsoft. Your ISP hasn't been very helpful as they dislike clients getting into the radios. I really don't blame them as it's incredible how many service calls we do on radios that get misprogrammed. That's why we set a unique IP for each radio and part of our programming blocks access from the Local Area Network. If you're able to access it though you could try setting a static IP in your router to: IP 169.254.1.99 Subnet 255.255.255.0 and use any DNS server you like within the range of 0-254 for each slot. Then you may be able to get through your router. Remember though to write down any info you will need to reenter to get back online.

B_B_T_D_B wrote: It's not neccessarily the router that has the problem. Vista added a whole new set of security measures that may be the problem. However, try pinging every point you can from your computer's IP to an external site such as Microsoft.com or google.com. Do "tracert www.microsoft.com" in a command prompt if you need the IPs to ping. Also, routers (more accurately called a "Residential Gateway") are prone to blocking such things. Check and see that there isn't a setting in the router that's discarding pings. Generally though it will only discard pings from the WAN, or outside your Local network. I did thorough testing with pings I initiated to various IPs. I did pings from my Vista computer command prompt, and pings from the http://network-tools.com/ website. All results from both were exactly the same. If one succeeded, the other succeeded. If one failed, the other failed too Thus my router is not generally interfering with pings. B_B_T_D_B wrote: As for why it works now and didn't before, probably an update from Microsoft. Your ISP hasn't been very helpful as they dislike clients getting into the radios. I really don't blame them as it's incredible how many service calls we do on radios that get misprogrammed. That's why we set a unique IP for each radio and part of our programming blocks access from the Local Area Network I agree that the radios should be left alone by the customers/clients. I don't have any reason to mess with the radio either, since it seems that the problem is between Vista and my router. That, of course, means that my ISP can wash their hands of the issue. B_B_T_D_B wrote: If you're able to access it though you could try setting a static IP in your router to: IP 169.254.1.99 Subnet 255.255.255.0 and use any DNS server you like within the range of 0-254 for each slot. Then you may be able to get through your router. Remember though to write down any info you will need to reenter to get back online.I have paid for a static IP from my ISP. Whether that static IP is set in the router, or the router is set for a dynamic IP, doesn't change the results.I tried changing the WAN static IP in the router to what you suggested, but then predictably could not access the Internet at all. Then I changed the LAN IP to that, and it didn't change the results. In both cases, I rebooted the router after the change.