Vista - Business Vista PC in Win 2000 domain

Hi everyone,

I try to include a business vista pc in a win 2000 domain. That worked
initially, but after a reboot the machine does not get the assigned IP of
192.168.1.X but this annoying 169.254.X.Y. Consequently the machine is not
part of the domain. I suspect it has something to do with the group policy
of the DC. Maybe some service is activated or deactivated but better should
not. The thing is we don't have that with XP or 2000 clients.
Anyone a good idea?

Regards
Michael

Does the DHCP run on a windows server? Or this link,

Vista Compatible issues
Troubleshooting Vista Remote Access Issues ... Networking between Vista and other Windows OS ... Info: Step by step troubleshooting VISTA sharing ...
http://www.chicagotech.net/vista/vista.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Michael Bender" <technik@salescom.de> wrote in message news:5igko7F3b4vcvU1@mid.individual.net...
Hi everyone,

I try to include a business vista pc in a win 2000 domain. That worked
initially, but after a reboot the machine does not get the assigned IP of
192.168.1.X but this annoying 169.254.X.Y. Consequently the machine is not
part of the domain. I suspect it has something to do with the group policy
of the DC. Maybe some service is activated or deactivated but better should
not. The thing is we don't have that with XP or 2000 clients.
Anyone a good idea?

Regards
Michael

Thx for the answer. I guess I have to be more precise.

Here's what I do:
An IP-adress is reserved in the DHCP on the WIN 2000 Server for every client
for the specific MAC-address of each machine. I installed Vista, reserved an
IP for this machine and logged on with a local account. I did get an IP and
kept it (even after rebooting). By the time I include the pc in the domain,
I do get an (or rather keep) IP aswell. After a reboot or presumably the
amount of time the group policies get effective the machine gets the
169.254.X.Y - IP . So I suspect somewhere in the jungle of the gpo some
setting is responible for "losing" the assigned IP. Again, this does not
happen with XP or 2000 clients.





"Robert L [MVP - Networking]" <noreply@hotmail.com> schrieb im Newsbeitrag
news:O7fVco43HHA.4712@TK2MSFTNGP04.phx.gbl...
Does the DHCP run on a windows server? Or this link,

Vista Compatible issues
Troubleshooting Vista Remote Access Issues ... Networking between Vista and
other Windows OS ... Info: Step by step troubleshooting VISTA sharing ...
http://www.chicagotech.net/vista/vista.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Michael Bender" <technik@salescom.de> wrote in message
news:5igko7F3b4vcvU1@mid.individual.net...
Hi everyone,

I try to include a business vista pc in a win 2000 domain. That worked
initially, but after a reboot the machine does not get the assigned IP of
192.168.1.X but this annoying 169.254.X.Y. Consequently the machine is not
part of the domain. I suspect it has something to do with the group policy
of the DC. Maybe some service is activated or deactivated but better
should
not. The thing is we don't have that with XP or 2000 clients.
Anyone a good idea?

Regards
Michael

You may want to try Microsoft update. this link may help,

Router and DHCP compatible issue – Solutions: upgrade the firmware, disable the IPv6, re-configure the speed, load Microsoft update, disable SPI and setup TCP/IP manually.

Vista Compatible issues
http://www.chicagotech.net/vista/vistacompatible.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Michael Bender" <technik@salescom.de> wrote in message news:5iie2rF3p7o9rU1@mid.individual.net...
Thx for the answer. I guess I have to be more precise.

Here's what I do:
An IP-adress is reserved in the DHCP on the WIN 2000 Server for every client
for the specific MAC-address of each machine. I installed Vista, reserved an
IP for this machine and logged on with a local account. I did get an IP and
kept it (even after rebooting). By the time I include the pc in the domain,
I do get an (or rather keep) IP aswell. After a reboot or presumably the
amount of time the group policies get effective the machine gets the
169.254.X.Y - IP . So I suspect somewhere in the jungle of the gpo some
setting is responible for "losing" the assigned IP. Again, this does not
happen with XP or 2000 clients.





"Robert L [MVP - Networking]" <noreply@hotmail.com> schrieb im Newsbeitrag
news:O7fVco43HHA.4712@TK2MSFTNGP04.phx.gbl...
Does the DHCP run on a windows server? Or this link,

Vista Compatible issues
Troubleshooting Vista Remote Access Issues ... Networking between Vista and
other Windows OS ... Info: Step by step troubleshooting VISTA sharing ....
http://www.chicagotech.net/vista/vista.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Michael Bender" <technik@salescom.de> wrote in message
news:5igko7F3b4vcvU1@mid.individual.net...
Hi everyone,

I try to include a business vista pc in a win 2000 domain. That worked
initially, but after a reboot the machine does not get the assigned IP of
192.168.1.X but this annoying 169.254.X.Y. Consequently the machine is not
part of the domain. I suspect it has something to do with the group policy
of the DC. Maybe some service is activated or deactivated but better
should
not. The thing is we don't have that with XP or 2000 clients.
Anyone a good idea?

Regards
Michael

You may find if you leave the computer on and do a release of IPs it will
finally get to the 2000 DHCP server. The 169 IP is the default windows uses
when it can't find another from a DHCP. Try putting the DHCP server's IP in
the default gateway. Also check you have good signal strength if WLAN.

"Michael Bender" <technik@salescom.de> wrote in message
news:5igko7F3b4vcvU1@mid.individual.net...