Friday, June 09, 2006 4:56 PM
I've done a fresh install of both the 64 bit and 32 bit Vista. I can't get online. I can ping the DNS server and I see data being sent and recieved but I can't view a web page. I run the diagonse tool and get a vaque message. "Windows found a problem that cannot be repaired automatically. Contact your internet Service provider or network administrator for help or click here for mor information about thing you can try to help resolve the problem". Before the computer had suse linux and it worked fine. I have other computers on the network and they work fine. Any ideas?
Friday, June 09, 2006 6:13 PMlHave you checked all of the standard stuff? Can you connect to local machines? NSLOOKUP showing valid info? NIC driver compatable with VISTA? Proxie settings correct? I have installed VISTA on several machines and on Virtual Server and all have worked fine for internet access. I don't expect I have been of much help, but perhaps you missed some of the basics.
Friday, June 09, 2006 6:34 PM
I have checked everything. I was even able to join a domain and ping the outside dns. I'm not missing any devices and as I said before I can see data being sent and recieved.
Friday, June 09, 2006 8:51 PMCan you access internal web sites? It is beginning to sound a bit like a firewall issue.
Friday, June 09, 2006 9:00 PM
Yes I can. I've tried turning off the firewall and everything else. Same response.
Friday, June 09, 2006 9:50 PM
If you can access internal web sites and external DNS, one of two things is probably the problem. Your proxy settings might be incorrect in the browser or your network firewall is preventing access from your computer. If the firewall (not windows Firewall, your real network firewall) rules are based on IP address you may have to change your address to the one that was previously allowed or make a new rule for the address it now has. HTH.
Friday, June 09, 2006 10:27 PM
I have no firewall software installed. All I have installed is windows vista. I have tried turning off the windows firewall no work. You may think this is crazy but no of this makes sense. The only thing I can think is that may be microsoft doesn't like my ZyXEL router. The nic card is a realtek. I just don't know what the hell is going on. Does microsoft get involved with this stuff at all. I have reinstalled the operating system 3 times. I've been doing this for over 25 years, I've worked with all forms of UNIX and have worked with windows since 1.0. Is Vista expecting a port to be open in the router? No Proxy in Use.
Saturday, June 10, 2006 3:52 AM
I have two networks in my shop one has my domain the other is mainly for fixing and updating computers. I'm going to connect to my second network with a Dlink router and see if I can get online. If I can and there is a problem with the ZyXEL router who and how do I report it?
Saturday, June 10, 2006 4:29 PM
After trying everything in the world I'm finally online. I changed to a diffirent network and router and now it works. Now if only someone would respond to how to report this to microsoft. For some reason I can't use my ZyXEL router with Vista. This router is not a cheap one so hopefully someone can help me to get it working. I want my customers to see what is coming next with microsoft but, I can't display it cause my retail area is connect to the ZyXEL router and my network domain.
Sunday, June 11, 2006 5:14 AM
I'm sorry I didn't see this thread earlier.
To report problems to Microsoft, download the Microsoft Beta Client from the following URL: http://go.microsoft.com/fwlink/?LinkId=43655 . This will enable you to file bugs directly and provide the required information. Make sure you provide an e-mail address so the developer assigned to your bug can contact you for further information.
Tuesday, June 13, 2006 2:42 PM
i have excatly the same problem than twnclick.
I am also a professionnal in IT, and i alreday tried everything.
Hope an answer, it's strange. Probably a proxy pb in vista ...
Wednesday, June 14, 2006 6:17 AMWhat kind of router and internet connection do you have? I've complained to the router company and haven't heard a word. Seems no one gets concerned unless it affects thousands of people. I'm going to try and call ZyXEL and request an RMA and see what they say. The router is on 3 months old and it's suppose to be one of the best.Hook it to a cheap Dlink and I'm off and running on the internet. You'd think that having a computer store with lots of potential future customers of windows they'd care.
Wednesday, June 14, 2006 6:25 AMI downloaded the beta software to my laptop and I will send information tomorrow. Thanks for the information as soon as I can get back on line with the vista computer I'll install it there so I can report problems quicker. Thanks again I sure hope we can figure out what is going on. I also sent an email to router company.
Wednesday, June 14, 2006 7:25 AM
I just tested with an AliceBox (modem/router from my ISP) with a 8Mbits connexion.
Bu I am sure that i would have the same problem with a Netopia or a Zyxel router.
I try to modified firewall rules in Vista using "mmc" command. No result. Without firewall, same thing.
I tested all parameters in Internet explorer 7, but i still have the problem.
I can display Google website for example, joga.com too. But impossible to connect on microsoft website.
How many website have you tested ?
Friday, June 16, 2006 6:52 PMYeh I am having the same problem with a Sonicwall Router. I can view and log into eveyone else's computer on the network but will not find hardly any outside websites. It does like www.google.com and a few other IP address's i put in manually... but there's something funky LOL
Monday, June 19, 2006 3:18 AM
I too have been having issues with DNS lookups by Vista, and this of course means that I cannot get my copy of Vista to activate.
I can reach the outside world on the connection, but I cannot get a response of any form from DNS.
If I wish decent response from a TRACERT then I have to use the -d switch to disable lookups or -n for PATHPING. This same behaviour occurs even if the Vista machine is placed naked in the DMZ.
Now there is no information I've been able to find to describe the default behaviour of the Network Settings, but my dialog tells me that my "Network Connected:" is Local until I actually attract the attention of the outside world, then it changes to Local and Intranet.
Like the hundreds of others experiencing this problem I've gone through the Firewall settings, disabled IPv6, and of course by placing the machine in the DMZ. This is definitely a DNS resolution error and would appear from other discussions about this same issue, that Vista is not using a commonly accepted method of doing DNS lookups.
From searches I've done the resolution has been to either completely re-install Vista or to update the BIOS in the routers. Since my Router is up-to-date I'm guessing that my only recourse is to re-install Vista, which seems like a solution that MS should be putting its best efforts into avoiding.
Monday, June 19, 2006 4:23 PM
It sounds to me like you all are experiencing the SPI bug. I was not able to connect to the internet when I installed Vista either, but a quick Google search led me to a site that says Vista's implementation of the TCP/IP stack completely crashes when it meets SPI ( Stateful Packet Inspection ) on your router. When I disabled this everything worked fine, doing so lessened the security of my network but hopefully MS will release an update soon addressing this issue.
Wednesday, June 21, 2006 6:30 PMI read elsewhere that some newer routers that use Stateful Packet Inspection (SPI) by default have issues with Vista networking. I haven't researched it enough to know where in the chain the problem resides. However, if you are using a router that includes SPI support and you can disable it, please disable the feature, try your Internet connection, and post back here if it works. The more information we have the better off we are. Thanks!
Wednesday, June 21, 2006 6:41 PM
I also have the same problem using a DLink router. I have not found an SPI disable option in my router configuration. Is this technology know by any other name?
My work around so far has been a Proxy server running on an XP box.
Wednesday, June 21, 2006 7:41 PM
Thanks to all of this chatting and a good night's sleep I was actually able to sit back and re-examine the problem I was having and solve it.
I had put a firewall rule on my router to block all protocols on all ports above 35,000 thinking that under no sensible situation would that ever be a problem, but:
Vista is simply screwy.
I sat back and ran NETSTAT again, taking a cold hard look at the returns and comparing them to my ruleset. Most of Vista's connections run in the 48,000 to 50,000 port number range, which of course my ruleset blocked. I opened up that range (having to create two new rulesets to accomplish that, a nasty limitation on DLink's part) and started getting results immediately after the router restarted.
It was suggested to me by our Infrastructure Manager that it may have been possible to use the router to forward the DNS requests rather than punch through the router to do so, so instead of pointing the DNS settings to external DNS servers you can point them at the router and the router may in fact be smart enough to know what to do with them.
My DI-704 isn't quite that smart.
Wednesday, June 21, 2006 7:44 PM
But Saska, wouldn't that require being able to actually use the internet effectively?
If DNS is pooched...
Wednesday, June 21, 2006 8:49 PMAgitprop: I'm not sure which of my comments you're referring to. Disabling SPI is done on the router.
Wednesday, June 21, 2006 9:46 PM
Agitprop: I'm not sure which of my comments you're referring to. Disabling SPI is done on the router.
You are correct in pointing out that my comments are cryptic viewed in some other manner than the one available to me. As your servers display the information to me my post comes immediately after your post about downloading a widget designed to talk to microsoft to tell microsoft that you can't talk to microsoft.
With that as a context you can now explain to us that the widget doesn't require DNS to talk with MS. (Instead requiring us to open up port 2600 to bi-directional UDP or somesuch tomfoolery).
Of course it was the irony that created the sarcasm.
Yes, I agree that SPI can be disabled on a router that allows SPI to be disabled, or that actually informs the user that SPI is an option. Many manufacturers (in a pique of efficiency) would rather spend 100 cents once to modify the visibility of the options available than spend 25 cents 10,000 times to break the option completely. They aren't Intel and these aren't 486s.
To be sure MS will rebuild the stack, or more likely put the last working stack back, for the RC - that is what Beta testing is all about. But that MS would break something this vital so far into the development cycle (face it, this is actually the beginning of the marketing cycle) seems to me to be nearly arrogant, certainly foolhardy.
The people who get these problems now are first adopters, they're the ones who had the releases prior to 5308 that didn't have these DNS issues and now they see MS screwing up. Certainly not a brilliant first step in the marketin cycle.
Still, all reports are that if you are willing to weaken your defenses against intrusion by disabling SPI (and DPI too) then Vista could very well work.
Running a NETSTAT and comparing Vista's expectations vs your router's rules may be all that you need to do though, as it was in my case where Vista only wanted to operate TCP/UDP on ports between 48,000 and 50,000, which included all of the DNS calls.
Monday, August 14, 2006 9:41 AMHello!
Nice to see that disabling spi in the router works for some people out ther, but i´m sorry to report that i´m still stuck.
I have disabled spi in my Linksys Rv042 router but the problem is still there.
Is there anybody with the same router that has got this to work ?
Monday, August 14, 2006 2:20 PM
have checked this?
please post back
Tuesday, August 15, 2006 8:15 AMHousab, i´ve allredy tried that patch. No change.
Tuesday, August 15, 2006 3:38 PMSeveral threads have mentioned the problem of getting on some web sites and not others. At least part of the problem (at least on many of lthe sites) is that the web site designers have put code to display the site a certain way depending on the browser type. IE7 is new and is not included in the code for these sites. When you try and access one of these sites with IE7 you can not get there. I don't know if the answer lies in Microsoft editing IE7 or the web sites re-writing their code. I would suggest contacting the webmaster of the site you are trying to access as well as submitting a bug report to MS.
Saturday, October 14, 2006 5:52 PM
You guys should look at this: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=755630&SiteID=17
Many people experience the same problem.