I created a image using WDS and syspreped each machine. The machines are getting the following warning when I try to install Mcafee agent on them, I reimaged one of the machines manually and it worked fine. Any work around besides disabling and enabling network card, I thinking this will have to be done often. TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.Charles

I would recommend workaround, namely the installation by group policy after deplyment of operating system. here is how to do it https://kc.mcafee.com/corporate/index?page=content&id=KB67796 Regards Milos

The problem seems to be with the computer and not ePO, will this fix the connection issue we have it on more than one machine that has the same image.

Hello, Since the issue is with McCafee installation, I would recommend asking in McCafee forums. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Thanks I understand what you are saying but its not a McAfee issue. All the machines that were imaged using the WDS have the TCP/IP issue. It just so happens that McAfee is the software that is being installed. Thanks. Charles

AHA :-) WDS uses multicast. If multicast is blocked on active network devices, that WDS would nor work. I would try WDS functionality on the same network, then I would double check switches or/and routers. Regards Milos

WDS will use unicast by default. You have to go out of your way to configure and implement multicast. I don't think this is his issue, as you either configure multicast right and it works, or you don't and it doesn't. It's a black-and-white scenario. Milos, the error is fairly clear, but what I'm curious about is the mechanics of the installation process. From the sounds of things, you're: Building the machine from WDSRebootingAttempting the installation of the McAfee software I'm not sure about the second bullet point - I'm just assuming, but what I it looks like is that independant of whether or not the reboot is in between, the network state has been reset and the subsequent McAfee installation is attempting to take place within the TIME_WAIT period for the source and destination port combination. If you have the ability to run commands before you execute the installation of the McAfee software, you can run these two commands to automate the resetting of the network adapter: netsh interface set interface name="Local Area Connection" admin=disabled netsh interface set interface name="Local Area Connection" admin=enabled Cheers, Lain

you should ask here:http://social.technet.microsoft.com/Forums/en-US/winserversetup/threadsJeff Ren TechNet Community Support beneficial to other community members reading the thread.