I have a 2003 domain at the office, IP v6 is not running on the DC.Doing a clean install of Win 7 build 7100 I was able to join the domain with no issues.The strange thing that happens though, is that when I power off the machine then power it back on, I lose connectivity to the domain (at least that is what I think happens) as under Network Sharing Centre I receive a message that the machine is connected to an "unidenfied network".The way I found to reconnect to the domain, was to move the Win 7 machine to a workgroup and then re-attach it to the domain.Would switching on IP v6 on the DC make this "go away"?TIA

Are you running DHCP or static IP. I had this issue with some Vista Pc's that where using DHCP and soon as I put all the Static info in including DNS and gateway it quit others would work fine even same brands of PC's that where identicall.Tim Comes

Are you running DHCP or static IP. I had this issue with some Vista Pc's that where using DHCP and soon as I put all the Static info in including DNS and gateway it quit others would work fine even same brands of PC's that where identicall. Tim Comes Running DHCP on the Win 7 box, except for having entered the server DNS ip.Will give it a try to enter all the information as "hard coded" and see what happens.Thanks!

Ok, that worked! Putting in the static info resolves this.Could this be just a "feature" of the RC product?

What kind of NIC is in the machine running Win 7? I had the same issue with one of my machines that had a nVidia NIC in it, which I had to statically setup the IP info. The Broadcom and Intel NICS I have seem to work fine with DHCP.

Leaving ipv6 enabled on your Windows 7 PC will not adversly affect your PC's ability to join an ipv4 network. In fact, Microsoft highly recommends you leave ipv6 enabled on client PCs.http://technet.microsoft.com/en-us/magazine/2009.07.cableguy.aspxI had troubles in our network until we provided information our logon script needed to handle windows 7 PCs. Basically, we have the logon script set to do different things on different OSs and there wasn't a provision in place for Windows 7 at the time. After we updated the logon scripts and Group Policy, it works flawlessly now.Hope some of that helps.

What kind of NIC is in the machine running Win 7? I had the same issue with one of my machines that had a nVidia NIC in it, which I had to statically setup the IP info. The Broadcom and Intel NICS I have seem to work fine with DHCP. It is a Broadcomm NetExtreme Gigabit. Comes "standard" on the HP NC8430 laptop that I am using

Leaving ipv6 enabled on your Windows 7 PC will not adversly affect your PC's ability to join an ipv4 network. In fact, Microsoft highly recommends you leave ipv6 enabled on client PCs.http://technet.microsoft.com/en-us/magazine/2009.07.cableguy.aspxI had troubles in our network until we provided information our logon script needed to handle windows 7 PCs. Basically, we have the logon script set to do different things on different OSs and there wasn't a provision in place for Windows 7 at the time. After we updated the logon scripts and Group Policy, it works flawlessly now.Hope some of that helps. Question, are you running a 2008 domain? Reason for asking, is that I am still running a 2003 domain and that may be causing the issue.

Leaving ipv6 enabled on your Windows 7 PC will not adversly affect your PC's ability to join an ipv4 network. In fact, Microsoft highly recommends you leave ipv6 enabled on client PCs.http://technet.microsoft.com/en-us/magazine/2009.07.cableguy.aspxI had troubles in our network until we provided information our logon script needed to handle windows 7 PCs. Basically, we have the logon script set to do different things on different OSs and there wasn't a provision in place for Windows 7 at the time. After we updated the logon scripts and Group Policy, it works flawlessly now.Hope some of that helps. Question, are you running a 2008 domain? Reason for asking, is that I am still running a 2003 domain and that may be causing the issue. We are running a 2003 domain with 2003 sp2 domain controllers.edit: Just restating we are running a 2003 domain with ipv4 only.We intially tried running windows 7 pcs in our environment with ipv6 fully disabled. It was a disaster. Half the time any non-domain admin user taht logged onto the network,Group Policy and logon scripts would not run/apply.Leaving ipv6 enabled we get 100% success.Apparantly Windows Vista/2008 and up, Microsoft started employing various pieces of ipv6 to enhance ipv4 traffic. Mostly from a security standpoint, using teredo to wrap ipv6 traffic into an ipv4 UDP packet for greater stability/security.Steps i'd recommend:1. leave ipv6 enabled on your windows 7 devices (and anything vista/2008 and up).2. check your logon scripts. See if they are conditional to the OS, if so you will need to provide allowences for windows 7.3. Check group policy, see if the scripts launched are conditional to the OS.hope that helps.