windows server rras record other C/S address in SSTP tunnel over ipv6
We can see that Client/Server ipv6 addresses in RRAS MMC console are not the same with netstat log. In rras SSTP mode, client connect to server port 443/tcp. Using packet capture tool such as wireshark, I found netstat tells the right address. Why RRAS mmc console print strange C/S addresses, with the same ipv6 prefix /64 as the netstat answer. Radius auth/accounting records are the same with rras mmc console. The same problem found in windows server 2016. When switch to IKEv2 tunnel mode, addresses in MMC are the same with netstat. The problem was not found in ipv4 tunnel. DirectAccess feature is not enable. Is this C/S addresses transform a feature? What for? Maybe Directaccess?
Troubleshooting Common VPN issues on Windows Server 2012 R2 Essentials
First published on TechNet on Jun 11, 2014 [This post comes to us courtesy of Sabir Chandwale, Harshal Charde, Ajay Sarkaria and Rituraj Choudhary from Global Business Support] In our previous post, we covered steps involved in configuring VPN on Windows Server Essentials.BITS, IAS, VSS and RRAS May Stop Responding on SBS 2008 With a Particular NIC Driver
First published on TechNet on May 18, 2009 [Today's post comes to us courtesy of Justin Crosby and Damian Leibaschoff]We are investigating an issue with certain Intel PRO/1000 EB with I/O Acceleration network card drivers on Windows Server 2008 that can cause the BITS service to become unresponsive after a few hours to several days of operation.The Network Policy Server Service (IAS) Fails to Start or be Installed
First published on TechNet on Feb 20, 2009 [Today's post comes to us courtesy of Damian Leibaschoff and Wayne McIntyre] We have seen some cases where the Network Policy Server service fails to start, when this happens, functionality provided by TS Gateway (used in RWW) or Routing and Remote Access (RRAS) will also stop working.
