I have clients that connect to a Window Server 2008 R2 box via PPTP. They are able to successfully negotiate a connection and receive a local IP address, but are unable to access any internal network resources, nor access the Internet when connected.
There are no error messages or logged messages indicating a problem.
Today while doing some routine maintenance I discovered that my internet-connected network adapter was using a 6to4 tunnel to connect to my ISP. Some self-eduction on Teredo seemed to indicate quite a few potential security vulnerabilities with using the protocol. I have disabled my network adapter from using Teredo and it doesn't seem to impact my gateway in any way. Is there anything I am missing that should encourage me to turn it back on?
I have a Windows Server 2008 R2 installation that is acting as a DC. It has been operational without any problems since late August. All of a sudden, UNC share access experiences an issue where no-one (clients or the DC itself) can access the DC's shares. A reboot of the computer resolves the issue for a minimum time 24-hours, at which time UNC fails again. When this occurs, DNS appears to be fine, routing is fine, I can remote in the server by its FCDN, etc. There are no log entries that really indicate that there is a problem until clients and even the DC itself try to refresh Group Policy, which is accessed via a UNC share.
I realize that details are scant, so if you have any troubleshooting information I can go dig up and post, I would appreciate it.
One of the more interesting features of Windows Vista/7 is being able to set a photo to represent your user. This is nice on a standalone installation, but is there a way to set the photo in Active Directory so that the photo is consistent no matter where the user logs in across the domain?
I've setup a new Windows Server 2008 R2 installation with AD, Certificate Services, NPS, and RRAS. I have setup (using the wizard) the policies for 802.1x authentication using an Airport Extreme as my WAP, making sure that the correct certificate and user groups have access. My wireless clients are able to connect to the WAP just fine, but they become unresponsive when the credentials are sent. I don't see any errors in the error console. For laughs and giggles, I gave the WAP a wrong shared secret password and Windows properly errors out. After restoring it to the proper shared secret I still don't see any error even though clients are not able to connect.
I even fired up Wireshark to see what is happening and I see the authentication packets being forwarded on to the server. I also see the server returning what appears to be the certificate, but none of my clients (Windows XP/7, iPhone, etc.) respond to the response sent.
Using an identical setup with a Win2k3 box, I am able to set it up just fine.
Ideas why this isn't working in Windows 2008 R2?
UPDATE 18 AUG 2009: I decided to do several reinstalls of R2 to no avail. For laughs and giggles I installed a SP2 copy of plain ol' Windows Server 2008. Using the same exact setup, hardware, network topology, NPS access policies it worked perfectly fine how it was suppose to. I am not entirely sure, but I'm about to chalk this one up as a bug in R2. Has anyone else been able to get 802.1x wireless working on Windows Server 2008 R2???