Duplex Syntax When Ghosting A GX270 (Intel Pro1000)

Question

Hello,   Due to some issues we're having with our switches, I am having to force 100 Full Duplex at boot when trying to Ghost a GX270. I have tried the syntax in the sample Protocol.ini provided with the device driver, but to no avail. It never actually gives any indication that the NIC is using these settings. I've done this in the past with the E100 and it did give indication that the duplex speed had changed.   Here's the protocol.ini that I'm currently using.   network.setup]version=0x3110netcard=nu2$nic,1,NU2$NIC,1transport=tcpip,TCPIPlana0=nu2$nic,1,tcpipSLOT=0X0160 [tcpip]NBSessions=6DriverName=TCPIP$BINDINGS=NU2$NICLANABASE=0DisableDHCP=0SLOT=0X0160 [pktdrv]DriverName=PKTDRV$BINDINGS=NU2$NICintvec=0x60chainvec=0x66SLOT=0X0160SPEEDDUPLEX = 3   [NU2$NIC] ; Protocol.Ini section for the Intel(R) PRO/1000 Adapters DRIVERNAME = E1000$SLOT=0X0160SPEEDDUPLEX = 3 ;   NODE       = '00D00C123456'  ; override the burned in MAC address ;  SPEEDUPLEX = 0 ; 10Mbps  half duplex;             = 1 ; 10Mbps  full duplex;             = 2 ; 100Mbps half duplex;             = 3 ; 100Mbps full duplex ;  SLOT       = 7 ; set this for each NIC if using more than one ;  CACHEFLUSH = 1 ; set this if doing an unattended installation of;                   Windows NT 4.0 using this driver to make the initial;                   connection   Here is the sample protocol.ini DOS contents included with the driver.   ; Protocol.Ini section for the Intel(R) PRO/1000 Adapters    DRIVERNAME = E1000$ ;  NODE       = '00D00C123456'  ; override the burned in MAC address ;  SPEEDDUPLEX = 0 ; 10Mbps  half duplex;              = 1 ; 10Mbps  full duplex;              = 2 ; 100Mbps half duplex;              = 3 ; 100Mbps full duplex ;  SLOT       = 7 ; set this for each NIC if using more than one ;  CACHEFLUSH = 1 ; set this if doing an unattended installation of;                   Windows NT 4.0 using this driver to make the initial;                   connection   ***Note that the sample indicates a syntax used by spelling SPEEDDUPLEX but the actual protocol .ini created indicates spelling SPEEDUPLEX. I've tried both of them and couldnt get this to work..   Any help or insight would be greatly appreciated.

belvedere22 · Answer

Bump, any help would be greatly appreciated.

Networking, Internet, & Bluetooth

Was this post helpful?