This is very late but we faced a similar problem and resolved it like this: Take the first NIC and bind all your necessary protocols. Take the second NIC and bind at least TCP/IP but do NOT bind Client for MS Networking. That second MS Client Networking binding is what is messing you up.
> On Wednesday, September 03, 2008 5:37 AM JorisvanderStruij wrote:
> We have several Windows 2003 R2 servers and 1 of those is our WDS server.
> This server is up to date with all MS updates.
> The server is equipped with a Intel PRO/1000 MT Dual Port Server Adapter
> both of wich are connected to the same network and have IP addresses within
> the same subnet.
> What we would like to realise is a situation in where we want to use Adapter
> Data services (WDS/Fileshare etc).
>
> In the beginning we disabled Adapter #2 and installed/configured WDS to
> accompany our situation only using Adapter #1. With success. We are able to
> RISETUP and RIPREP (we use running in mixed mode for older XP situations
> atm.) with no problems.
>
> When we wanted to use Adapter #2 and use this explicitly for Data transfers,
> is when the fun started. After enabling the 2nd adapter WDS was unusable.
> The PXE boot and OSChooser phase is no problem. But after hitting <Enter> in
> the summary screen we get to the point where it goes wrong. Everything after
> this point goes extremely slow and after maby 10 min the famous missing NIC
> drivers error shows.
> I wanted to make use of the WDSUTIL /Set-Server /BindPolicy option to force
> WDS to use Adapter #2 for its data transfers, but i didnt even get to the
> stage as even the fact of enabling the 2nd adapter kills WDS.
> When is the disable the 2nd adapter everything goes as normal.
>
> I know the use of multiple nics is not preferred, but we realy want to
> realise this scenario. Simply enabling a 2nd adapter shouldn't be a show
> stopper for WDS in my opinion.
>
> We hope to find a solution for our situation.
>
> Some more info:
>
> C:\>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : SRVDC3
> Primary Dns Suffix . . . . . . . : secred.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : secred.com
>
> Ethernet adapter Core Services:
>
> Connection-specific DNS Suffix . : secred.com
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Server
> Adapter
> Physical Address. . . . . . . . . : 00-04-23-A7-F7-F8
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.6.0.10
> Subnet Mask . . . . . . . . . . . : 255.255.224.0
> Default Gateway . . . . . . . . . : 10.6.0.1
> DNS Servers . . . . . . . . . . . : 10.6.0.3
> 10.6.0.4
>
> Ethernet adapter Data Services:
>
> Connection-specific DNS Suffix . : secred.com
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Server
> Adapter #2
> Physical Address. . . . . . . . . : 00-04-23-A7-F7-F9
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.6.0.11
> Subnet Mask . . . . . . . . . . . : 255.255.224.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 10.6.0.3
> 10.6.0.4
> Submitted via EggHeadCafe - Software Developer Portal of Choice
> Autocorrelation method in C# for signal analysis
> http://www.eggheadcafe.com/tutorials...-analysis.aspx
Similar Threads
Linear Mode
