|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)
- [JIRA] (JENKINS-16163) NullPointerExcepti... [email protected] (JIRA)

You have IPv6 enabled on your Windows Server 2008 R2 systems, do you have IPv6 enabled? Is it possible to try with IPv6 disabled at the network connection level? I am still trying to find a system I can install Win2k8 on that will have IPv6 enabled, which I think is the culprit (but I am not sure yet). I don't know why this would have changed with any core changes though. I need to be able to replicate the issue locally (which I have no been able to do) before I can know for sure what needs to be done.