vista 5384 networking dns s

I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

"gregom" wrote:

I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

I have the same problem using NVIDIA nForce3, I think that I'll buy a new network card.
-- C/Cpp Programmer ..NET Programmer C# Programmer Java?? No thanks :D

I have the same problem using NVIDIA nForce3, I think that I'll buy a new network card.
-- C/Cpp Programmer ..NET Programmer C# Programmer Java?? No thanks :D
"gregom" wrote:

I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

I can see why you'd think another NIC would help, but in my case it's clearly not the card, since even connecting via a Wireless card produces the same effect.
I think I might try reinstalling from scratch raher than an upgrade install - must be a networking config issue.
The fact I can ping an Internet site but not resolve it proves there's nothing wrong with the card.
"Brave Belzebuth" wrote:

I have the same problem using NVIDIA nForce3, I think that I'll buy a new network card.
-- C/Cpp Programmer .NET Programmer C# Programmer Java?? No thanks :D
"gregom" wrote:
I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

Magyar, try manually adding your ISPs DNS servers to your preferred DNS servers.
-- Jane, not plain ;) 64bit enabled ;) Batteries not included. Braincell on vacation ;) "Magyar Poster" wrote in message

I can see why you'd think another NIC would help, but in my case it's clearly not the card, since even connecting via a Wireless card produces the same effect.
I think I might try reinstalling from scratch raher than an upgrade install - must be a networking config issue.
The fact I can ping an Internet site but not resolve it proves there's nothing wrong with the card.
"Brave Belzebuth" wrote:
I have the same problem using NVIDIA nForce3, I think that I'll buy a new network card.
-- C/Cpp Programmer .NET Programmer C# Programmer Java?? No thanks :D
"gregom" wrote:
I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

Jane Tried that - that's the DNS server I said I could ping but not resolve from. It's definitely working as a tried the same manual config on another machine and it's fine. I've tried disabling all the non-critical networking like the LAN topology stuff, but no avail.
"Jane C" wrote:

Magyar, try manually adding your ISPs DNS servers to your preferred DNS servers.
-- Jane, not plain ;) 64bit enabled ;) Batteries not included. Braincell on vacation ;) "Magyar Poster" wrote in message I can see why you'd think another NIC would help, but in my case it's clearly not the card, since even connecting via a Wireless card produces the same effect.
I think I might try reinstalling from scratch raher than an upgrade install - must be a networking config issue.
The fact I can ping an Internet site but not resolve it proves there's nothing wrong with the card.
"Brave Belzebuth" wrote:
I have the same problem using NVIDIA nForce3, I think that I'll buy a new network card.
-- C/Cpp Programmer .NET Programmer C# Programmer Java?? No thanks :D
"gregom" wrote:
I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

The only other things that spring to mind are disabling any ipv6 and SPI if your router has it.
-- Jane, not plain ;) 64bit enabled ;) Batteries not included. Braincell on vacation ;) "Magyar Poster" wrote in message

Jane Tried that - that's the DNS server I said I could ping but not resolve from. It's definitely working as a tried the same manual config on another machine and it's fine. I've tried disabling all the non-critical networking like the LAN topology stuff, but no avail.
"Jane C" wrote:
Magyar, try manually adding your ISPs DNS servers to your preferred DNS servers.
-- Jane, not plain ;) 64bit enabled ;) Batteries not included. Braincell on vacation ;) "Magyar Poster" wrote in message I can see why you'd think another NIC would help, but in my case it's clearly not the card, since even connecting via a Wireless card produces the same effect.
I think I might try reinstalling from scratch raher than an upgrade install - must be a networking config issue.
The fact I can ping an Internet site but not resolve it proves there's nothing wrong with the card.
"Brave Belzebuth" wrote:
I have the same problem using NVIDIA nForce3, I think that I'll buy a new network card.
-- C/Cpp Programmer .NET Programmer C# Programmer Java?? No thanks :D
"gregom" wrote:
I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

I've already disabled IPv6 but as for SPI I suppose it might be - just assumed that if one Vista machine (my laptop) can get a DHCP address OK then there's nothing wrong with the router.
I have to say I'd never heard of SPI before today and had to look it up....
"Jane C" wrote:

The only other things that spring to mind are disabling any ipv6 and SPI if your router has it.
-- Jane, not plain ;) 64bit enabled ;) Batteries not included. Braincell on vacation ;) "Magyar Poster" wrote in message Jane Tried that - that's the DNS server I said I could ping but not resolve from. It's definitely working as a tried the same manual config on another machine and it's fine. I've tried disabling all the non-critical networking like the LAN topology stuff, but no avail.
"Jane C" wrote:
Magyar, try manually adding your ISPs DNS servers to your preferred DNS servers.
-- Jane, not plain ;) 64bit enabled ;) Batteries not included. Braincell on vacation ;) "Magyar Poster" wrote in message I can see why you'd think another NIC would help, but in my case it's clearly not the card, since even connecting via a Wireless card produces the same effect.
I think I might try reinstalling from scratch raher than an upgrade install - must be a networking config issue.
The fact I can ping an Internet site but not resolve it proves there's nothing wrong with the card.
"Brave Belzebuth" wrote:
I have the same problem using NVIDIA nForce3, I think that I'll buy a new network card.
-- C/Cpp Programmer .NET Programmer C# Programmer Java?? No thanks :D
"gregom" wrote:
I'm having a similar problem... but even setting an IP doesnt get me anywhere. I am receving 0 packets, no matter what I try.
I'm using a BioStar iDeq 200N that comes with nVidia 2 chipset I believe.
Vista detected the card fine, and says its working... It just cant find my network.
I'm using a Netgear WGR614 v4 router and all my other computers work fine. Never had a problem like this before. I even tried turning off Windows firewall... nothing.
I can't see other comptuers on the network or anything, it just sends packets, but doesnt receive any.

I had this to, but I have searched for the problem and it was not Windows Vista, but my router. I have installed the newest firmware and it worked. Maybe it's also the problem with you.
Greetz Jan
"Magyar Poster" wrote in message

I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

Well, it was solved in the end by doing a fresh install, overwriting the original windows - I guess it was just one of those things.
"Jan Wynen" wrote:

I had this to, but I have searched for the problem and it was not Windows Vista, but my router. I have installed the newest firmware and it worked. Maybe it's also the problem with you.
Greetz Jan
"Magyar Poster" wrote in message
I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

Hmm yeah, I tried disabling the IPv6 and topology stuff too and it did nothing. I also was one who tried manually putting in my ISP's DNS servers in. I've tried everything I can think of. Every logical settings says "it should work", but it simply, doesn’t.
I checked my router too, I don't see anything for SPI so I'm assuming it does not have it. Or... it does and just doesn’t give an option to disable it.
Perhaps a router firmware update would help... As for the fresh install of Vista, thats another option as well, I did the install of Vista onto another partition along with 32-bit XP. XP still works fine and connects to my network/internet fine as well.
I think this is probably just a major bug in the beta2 release...
I hope someone at Microsoft is reading this, because sometimes I wonder if you even test things at all. You guys really gotta do a lot more thorough, more complete testing of your product on several different systems and configurations. I know it costs a lot of money to do this, but you've got tons of resources, just do your (prospective) customers a favor and test this stuff before it comes to us.
I hope the official release doesn’t have as many bugs... but I suppose it will. In the past its always been first release, tons of bugs, fix with SP1... then fix small things and annoyances with SP2. Finally by SP3 its a decent, solid OS.
I think more money should be spent on quality assurance and testing.

I sent through some comments to Microsoft about this (in fairness, this IS a beta release - yes, if MS release a buggy final version then that's wrong, but a beta is meant for testing!)
Having said that, I do like the topology stuff now it's working! I imagine that's going to be very useful for small businesses.
"gregom" wrote:

Hmm yeah, I tried disabling the IPv6 and topology stuff too and it did nothing. I also was one who tried manually putting in my ISP's DNS servers in. I've tried everything I can think of. Every logical settings says "it should work", but it simply, doesn’t.
I checked my router too, I don't see anything for SPI so I'm assuming it does not have it. Or... it does and just doesn’t give an option to disable it.
Perhaps a router firmware update would help... As for the fresh install of Vista, thats another option as well, I did the install of Vista onto another partition along with 32-bit XP. XP still works fine and connects to my network/internet fine as well.
I think this is probably just a major bug in the beta2 release...
I hope someone at Microsoft is reading this, because sometimes I wonder if you even test things at all. You guys really gotta do a lot more thorough, more complete testing of your product on several different systems and configurations. I know it costs a lot of money to do this, but you've got tons of resources, just do your (prospective) customers a favor and test this stuff before it comes to us.
I hope the official release doesn’t have as many bugs... but I suppose it will. In the past its always been first release, tons of bugs, fix with SP1... then fix small things and annoyances with SP2. Finally by SP3 its a decent, solid OS.
I think more money should be spent on quality assurance and testing.

Yeah I understand that and its all good, but it just feels like MS is making the users the 'quality assurance group'. Why bother do your own testing and pay for allt he equipment to test it on when you can have your users do it for you?
This seems like a rather large networking bug, going across a lot of nvidia based motherboards.
Anyway I don't want to try to upgrade my router, and I don't particularly want to re-install the OS again.
I'd just like the bug fixed so I can use the OS and submit all the error reports and of course my coments on it. Kind of hard to do that when it wont even connect to the network.

"Magyar Poster" wrote:

I sent through some comments to Microsoft about this (in fairness, this IS a beta release - yes, if MS release a buggy final version then that's wrong, but a beta is meant for testing!)
Having said that, I do like the topology stuff now it's working! I imagine that's going to be very useful for small businesses.
"gregom" wrote:
Hmm yeah, I tried disabling the IPv6 and topology stuff too and it did nothing. I also was one who tried manually putting in my ISP's DNS servers in. I've tried everything I can think of. Every logical settings says "it should work", but it simply, doesn’t.
I checked my router too, I don't see anything for SPI so I'm assuming it does not have it. Or... it does and just doesn’t give an option to disable it.
Perhaps a router firmware update would help... As for the fresh install of Vista, thats another option as well, I did the install of Vista onto another partition along with 32-bit XP. XP still works fine and connects to my network/internet fine as well.
I think this is probably just a major bug in the beta2 release...
I hope someone at Microsoft is reading this, because sometimes I wonder if you even test things at all. You guys really gotta do a lot more thorough, more complete testing of your product on several different systems and configurations. I know it costs a lot of money to do this, but you've got tons of resources, just do your (prospective) customers a favor and test this stuff before it comes to us.
I hope the official release doesn’t have as many bugs... but I suppose it will. In the past its always been first release, tons of bugs, fix with SP1... then fix small things and annoyances with SP2. Finally by SP3 its a decent, solid OS.
I think more money should be spent on quality assurance and testing.

hey jan wynen, just curious which router do you have? because i'm having lots of issues with my netgear WGR614 and SPI, and I don't really want to turn it off as there is no third party firewall for vista as of yet.
"Jan Wynen" wrote:

I had this to, but I have searched for the problem and it was not Windows Vista, but my router. I have installed the newest firmware and it worked. Maybe it's also the problem with you.
Greetz Jan
"Magyar Poster" wrote in message
I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

I have a Netgear WGR614 as I previously mentioned. I didn't see any SPI option earlier but since you mentioned I decided to check again, and it does have it. I disabled SPI but unfortunatly this had no effect on Vista.
Vista still is not receving any data at all on the network card. I tried several things, but it just wont work.
This kind of sucks... Vista is almost useless since I cant install anything or access the internet.
I'm considering the re-install option but I really don't want to do that... "Mitch R" wrote:

hey jan wynen, just curious which router do you have? because i'm having lots of issues with my netgear WGR614 and SPI, and I don't really want to turn it off as there is no third party firewall for vista as of yet.
"Jan Wynen" wrote:
I had this to, but I have searched for the problem and it was not Windows Vista, but my router. I have installed the newest firmware and it worked. Maybe it's also the problem with you.
Greetz Jan
"Magyar Poster" wrote in message
I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

Reinstalling doesnot help either. I also have the WGR614v6. I tried every option that I could think of, but the router is not returning any byte. I also read about the same problems with linksys routers. There should be fix for this poblem.
"gregom" wrote:

I have a Netgear WGR614 as I previously mentioned. I didn't see any SPI option earlier but since you mentioned I decided to check again, and it does have it. I disabled SPI but unfortunatly this had no effect on Vista.
Vista still is not receving any data at all on the network card. I tried several things, but it just wont work.
This kind of sucks... Vista is almost useless since I cant install anything or access the internet.
I'm considering the re-install option but I really don't want to do that... "Mitch R" wrote:
hey jan wynen, just curious which router do you have? because i'm having lots of issues with my netgear WGR614 and SPI, and I don't really want to turn it off as there is no third party firewall for vista as of yet.
"Jan Wynen" wrote:
I had this to, but I have searched for the problem and it was not Windows Vista, but my router. I have installed the newest firmware and it worked. Maybe it's also the problem with you.
Greetz Jan
"Magyar Poster" wrote in message
I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

Reinstalling doesnot help either. I tried every option you could think of. BTW I have the same router.
"gregom" wrote:

I have a Netgear WGR614 as I previously mentioned. I didn't see any SPI option earlier but since you mentioned I decided to check again, and it does have it. I disabled SPI but unfortunatly this had no effect on Vista.
Vista still is not receving any data at all on the network card. I tried several things, but it just wont work.
This kind of sucks... Vista is almost useless since I cant install anything or access the internet.
I'm considering the re-install option but I really don't want to do that... "Mitch R" wrote:
hey jan wynen, just curious which router do you have? because i'm having lots of issues with my netgear WGR614 and SPI, and I don't really want to turn it off as there is no third party firewall for vista as of yet.
"Jan Wynen" wrote:
I had this to, but I have searched for the problem and it was not Windows Vista, but my router. I have installed the newest firmware and it worked. Maybe it's also the problem with you.
Greetz Jan
"Magyar Poster" wrote in message
I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

In my case it doesn't matter wether I use the NForce3 or Realtek Gigabit Lan. In both cases the router's DHCP-Server returns a correct IP-Address (correct IP range - fitting the router's config), which can be seen in the network-connection details - however a 169.XXX.XXX.XXX - address gets assigned by Vista wich is definitely wrong.
There's an other thing I can reproduce: After entering the IP-Address manually (as written before DHCP doesn't work) only a few web-pages do actually work. I ran into trouble like this before with several Linux-distributions (Gentoo, Ubuntu, SuSE...) and therefor tryed the same I did there: I entered "real" DNS-Servers instead of my router's IP-Address (whose DNS-Forward actually works correctly) - and it worked. I'm a bit amazed, as I never ran into this bug with any Windows version (starting with 95) before... in my case only Linux-boxes have been affected (concerning Linux there might be a proper solution, but I never searched into this direction).
Regards
Kabelsalat


"Magyar Poster" wrote:

I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

In my case it doesn't matter wether I use the NForce3 or Realtek Gigabit Lan. In both cases the router's DHCP-Server returns a correct IP-Address (correct IP range - fitting the router's config), which can be seen in the network-connection details - however a 169.XXX.XXX.XXX - address gets assigned by Vista wich is definitely wrong.
There's an other thing I can reproduce: After entering the IP-Address manually (as written before DHCP doesn't work) only a few web-pages do actually work. I ran into trouble like this before with several Linux-distributions (Gentoo, Ubuntu, SuSE...) and therefor tryed the same I did there: I entered "real" DNS-Servers instead of my router's IP-Address (whose DNS-Forward actually works correctly) - and it worked. I'm a bit amazed, as I never ran into this bug with any Windows version (starting with 95) before... in my case only Linux-boxes have been affected (concerning Linux there might be a proper solution, but I never searched into this direction).
Regards
Kabelsalat


"Magyar Poster" wrote:

I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?

I tried the manual DNS with my ISP's and this didn't work... I'm glad it worked for you.
I think this is just a major bug with Vista... I don't really have the patience or time to mess with it.
I think I'm going to try installing the x64 version on my main computer. I've made a image of both my OS partitions just in case something goes wrong, hopefully I can restore my system.


"Kabelsalat" wrote:

In my case it doesn't matter wether I use the NForce3 or Realtek Gigabit Lan. In both cases the router's DHCP-Server returns a correct IP-Address (correct IP range - fitting the router's config), which can be seen in the network-connection details - however a 169.XXX.XXX.XXX - address gets assigned by Vista wich is definitely wrong.
There's an other thing I can reproduce: After entering the IP-Address manually (as written before DHCP doesn't work) only a few web-pages do actually work. I ran into trouble like this before with several Linux-distributions (Gentoo, Ubuntu, SuSE...) and therefor tryed the same I did there: I entered "real" DNS-Servers instead of my router's IP-Address (whose DNS-Forward actually works correctly) - and it worked. I'm a bit amazed, as I never ran into this bug with any Windows version (starting with 95) before... in my case only Linux-boxes have been affected (concerning Linux there might be a proper solution, but I never searched into this direction).
Regards
Kabelsalat


"Magyar Poster" wrote:
I am having problems with one of my machines running Vista Beta 2 (5384). Whenever I use DHCP to pick up an IP address, I get "limited or no connectivity" and a spurious IP of e.g. 169.254.59.155. This occurs irrespective of whether I connect via the built-in NIC (nForce 4 motherboard) or a USB wireless adaptor.
The same build works fine via the same wireless LAN using DHCP on a laptop.
If I manually set the IP to a valid address, I can ping my router (on 10.0.0.1) but, even though I give it a valid DNS server, I can't resolve FQDNs and can't web browse. Running the "Diagnose Internet Connection" confirms that it's a DNS problem.
Any ideas, anyone?