ML350 G6: NIC ML350 driver

Hello

I'm in a bit of a catch 22, since a driver update manager or windows may be able to find the right one, but I cannot connect to the internet, and to connect to the internet, I need the diver.

I have a ML350 G6 run a clean install of Win7 pro x 64 and it will not recognize or connect to my network. I tried to plug a cat6 ethernet in the two ports on the computer, but nothing helped. But, network activity are lit on connected port and the front of the Tower, and the switch recognizes that a device is connected. All my other computers connect properly, so the modem and the switch are not the problem.

Device Manager shows missing drivers for the network card, device Base system and the interface of the IMPI.

The icon of the status bar displays a red X, said convenience store there is no network card driver and can not fix the problem.

Can you help me find and direct me to a downloadable .exe driver for this problem? I tried HP support research and the internet for several days but came up empty. Can I download it on another computer and then install it on the server via a hot-swap drive.

If you need more information, direct me where, and I'll be happy to provide.

Thanks in advance for your help.

Sorry this ethernet driver did not work.

See if this works instead... go to Device Manager, right-click on the broadcom ethernet adapter and select uninstall.

Check the box uninstall driver.

Reboot and try the driver ethernet directly from Broadcom.  This is for all operating systems.

You want the 64-bit driver (2nd group of adapters under the section of the conductors).

http://www.Broadcom.com/support/Ethernet-NIC-NetXtreme-i-server

As there is no exe file to install it with, the above driver must be manually installed.

Download and uncompress the file in its folder.

Go to Device Manager and click on the ethernet controller needing drivers.

Click the driver tab.  Click on set to update driver.

Select her browse my computer for driver software option and navigate to the driver folder, that you unzipped.

Make sure that the include subfolders is selected and see if the driver will install.

I hope that one will work.

The other device ID (PCI\VEN_103C & DEV_3302) that you posted needs this driver...

http://h20565.www2.HPE.com/hpsc/SWD/public/detail?sp4ts.Oid=3884318 & swItemId = MTX_f5c1247ce2574854b076e45b9b & swEnvOid = 4064 #.

Tags: HP Desktops

Similar Questions

  • NIC & Storage Driver Version and Firmware

    Hello

    I would like to know powercli average to determine the firmware revision, version, and NETWORK/storage card driver name. I can take this info via

    esxcfg-info takes so long

    ethtool-i vmnic0

    Thank you

    The seller and the device to take a look at my post to appoint this material .

    According to the HW you use, you can try using the CIM for the information.

    Take a look at the BIOS of ESX, NIC and HBA driver Versions, which shows a way to do with HP hardware.

  • HP 15-d103 found NIC controller/driver

    Sir my hardware/device id are:
    PCI\VEN_168C & DEV_0036 & SUBSYS_217F103C & REV_01
    PCI\VEN_168C & DEV_0036 & SUBSYS_217F103C
    PCI\VEN_168C & DEV_0036 & CC_028000
    PCI\VEN_168C & DEV_0036 & CC_0280
    Please give me the link to download driver for network controller

    model: hp 15-d103tx notebook pc (G2G48PA #ACJ)

    Series No.: [number of Series edited by Moderator]
    I installed windows 7 ultimate 64 bit

    Hello:

    Here is the link for the driver you need...

    http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswItem%253Dob_128686_1&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

  • HP Probook 6560 b r2 2012 nic network driver

    My network card has no driver after upgrade to Windows server R2 de Windows server 2012, 2012.

    Does Anyobody know where the driver or a replacement driver can be obtained?

    It does not appear when I look at hp support.

    you had it almost right,

    What should be done:

    Download and install this free utility for files...

    http://www.7-zip.org/

    After installing 7 - Zip, download, but do not run the Intel ethernet driver.

    Right-click on the Intel ethernet driver file and select 7 - Zip option in the menu.

    Have 7-Zip extract of: and I select the file name to extract the drivers to a folder.

    Copy this folder to the root of the c:

    Now with Explorer, go to: 'C:\PROWinx64\PRO1000\Winx64\NDIS64 '.

    Right click on the file "e1c64x64.inf" and say edit

    Remove the 3 lines under the [ControlFlags]

    Copy the last 4 lines of [Intel.NTamd64.6.3.1] (lines are in bold)

    [Intel.NTamd64.6.3.1]
    ; DisplayName Section DeviceID
    ; -----------                   -------              --------
    % E1502NC. DeviceDesc % = E1502.6.3.1, PCI VEN_8086 & DEV_1502
    % E1502NC. DeviceDesc % = E1502.6.3.1, PCI VEN_8086 & DEV_1502 & SUBSYS_00008086
    % E1502NC. DeviceDesc % = E1502.6.3.1, PCI VEN_8086 & DEV_1502 & SUBSYS_00011179
    % E1502NC. DeviceDesc % = E1502.6.3.1, PCI VEN_8086 & DEV_1502 & SUBSYS_00021179
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503 & SUBSYS_00008086
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503 & SUBSYS_00011179
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503 & SUBSYS_00021179

    Paste the copied lines to [Intel.NTamd64.6.3], with the result the textfragment below

    [Intel.NTamd64.6.3]
    ; DisplayName Section DeviceID
    ; -----------                   -------        --------
    % E1502NC. DeviceDesc % = E1502, PCI VEN_8086 & DEV_1502
    % E1502NC. DeviceDesc % = E1502, PCI VEN_8086 & DEV_1502 & SUBSYS_00008086
    % E1502NC. DeviceDesc % = E1502, PCI VEN_8086 & DEV_1502 & SUBSYS_00011179
    % E1502NC. DeviceDesc % = E1502, PCI VEN_8086 & DEV_1502 & SUBSYS_00021179
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503 & SUBSYS_00008086
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503 & SUBSYS_00011179
    % E1503NC. DeviceDesc % = E1503.6.3.1, PCI VEN_8086 & DEV_1503 & SUBSYS_00021179

    Now, save the file.

    Since the metro screen type cmd, right click and choose "Run as Administrator" for a guest back

    Now type: bcdedit - set loadoptions DISABLE_INTEGRITY_CHECKS 
    Now type: bcdedit-set TESTSIGNING

    REBOOT the laptop

    Now with Explorer, go to: 'C:\PROWinx64\PRO1000\Winx64\NDIS64 '.

    Right click on the file "e1c64x64.inf" and say install

    A warning appears asking if you want to install the no checked pilot--> Yes

    The driver will be installed

    Since the metro screen type cmd, right click and choose "Run as Administrator" for a guest back

    Now type: bcdedit - set loadoptions ENABLE_INTEGRITY_CHECKS 
    Now type: bcdedit - set off the TESTSIGNING

    Reboot the laptop

    Fact!

    Happy as a hippo

  • Start since the. ISO converter can not see paravirtual (or NIC) scsi drives

    From time to time I develop the C:\ on Windows boot drive using the method #2 in the link below. IE use the V2V Converter a VM and resize the C:\ drive, then trash the old VM and keep the new virtual machine with the Boot disk more.

    -LINK-

    I understand PVSCSI drives are now supported as boot post ESX4 U1 disks, however, I found I can no longer use this method #2 (above) to extend a boot disk.

    One of the other methods on the links above will work? I understand w / provisioning end it becomes less as a problem, but he slips always upwards from time to time the drive C:\ requires more space.

    The attached screenshot shows a 32-bit of 2 k 3 virtual machine using the PVSCSI starts from the conveter. ISO.  Since the C:\ and a single disc is on the PVSCSI vAdapter no OS can be found and I get the error "Unable to determine the operating system invited".  If you have multiple SCSI cards on the virtual machine (and drive), the LSI (and others) discs can be seen and converted.  But without convert them the boot disk, it's kinda useless.

    Will be updated soon converter .iso image file to include the PVSCSI drivers?  It seems the paravirutal NETWORK card driver is required for this converter can cling to the VC or the host as well.

    Thank you.

    Jonathan

    Hi, if you increment the Vsphere Client disk space, the guest sees the added extra space?

    If you can see the added space, try Dell extpart, it is a very good tool, free, and you don't need to stop the virtual machine to expand disk space.

    Check this link http://ftp.dell.com/app/ExtPart.txt

    Here is the link to download the http://support.dell.com/support/downloads/download.aspx?c=us&cs=19&l=en&s=dhs&releaseid=R64398&formatcnt=2&fileid=83929 app

    I used this tool several times and it has worked very well.

  • Driver NIC in windows vista

    Install a nic card driver in windows vista (network everywhere nc100 or 3com-38928497) can't seem to find if they are compatible or drivers for them. Thank you

    Hello
     
    By your post what we mean is that Vista does not recognize the network adapter driver or is not compatible. Is this fair?

    Check if there is no exclamation point on any of the items in the Device Manager.
    http://Windows.Microsoft.com/en-us/Windows-Vista/open-Device-Manager
     
    To check if the device is compatible with Vista, please visit this link:
    http://www.Microsoft.com/Windows/compatibility/Windows-Vista/
     
    To download the latest driver for the device, visit the device manufacturer's Web site or the website of the manufacturer of the system.
     
    Visit this link for more information:
    http://Windows.Microsoft.com/en-us/Windows-Vista/the-hunt-for-drivers-how-to-find-Windows-Vista-drivers-for-all-your-hardware
     
    Please provide us with more information, so that we can better help you.
     
    Kind regards
    Syed
    Answers from Microsoft supports the engineer.

  • BIOS of ESX, NIC and HBA driver Versions

    Hi friends,

    am intermiediate POWERCLI user and shell the scritping, please you colud help launch me script below.

    more information http://www.sandfordit.com/vwiki/ESX_Script_Extracts_and_Examples

    Thanks in advance,

    Aldo.

    Get versions of driver BIOS, NIC and HBA is dependent on what is reported to the ESX provider CIM material supplier. This script has been written using different servers of HP and well can work for them.

    # ===============================================================
    # ESX Inventory Getter
    # ===============================================================
    # Simon Strutt        November 2010
    # ===============================================================
    #
    # Version 1
    # - Initial Creation
    #
    # Version 2 - Dec 2010
    # - Added BiosVer, CpuCores, CpuModel, HbaModel, NicModel
    # - Bugfix: Corrected VC connection handling
    # - Removed dependency on obsoleted properties (from upgrade to PowerCLI v4.1.1)
    #
    # Limitations
    # - Tested on HP DL380 (G7), BL465 (G7), BL495 (G6), BL685 (G5)
    # - Supports 1 distinct HBA model, 2 distinct NIC models
    #
    # ================================================================
     
    $start = Get-Date
    $OutputFile = "ESXs.csv"
    $VC_List = "ESX-Check.csv"
    $UserFile = "User.fil"
    $PassFile = "Pass.fil"                           # Encrypted file to store password in
    $Results = @()
     
    # Include library files
    . .\lib\Standard.ps1
     
    Start-Transcript -Path ESX-Inventory.log
    Log "Started script run at $start"
     
    # Function-U-like ===================================================================================
     
    Function Get-NicDriverVersion ($view, $driver) {
        # Gets the CIM provided driver version (tallies up driver name with CIM software component)
        $result = ($view.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like $driver + " driver*"} | Get-Unique).Name
        $result = ([regex]::Matches($result, "(\b\d)(.*)(?=\s)"))[0].Value         # HP regex to extract "2.102.440.0" for example
        $result
    }
     
    # =================================================================================================== 
     
    # Load list of VC's
    try {
        $VCs = Import-CSV $VC_List
    } catch {
        Log "ERROR: Failed to load list of vC's"
        Exit
    }
     
    # Load password credential from encrypted file
    $pass = Get-Content $PassFile | ConvertTo-SecureString
    $user = Get-Content $UserFile
    $cred = New-Object System.Management.Automation.PsCredential($user, $pass)
     
    foreach ($vc in $VCs) {
     
        # Connect to VC
        try {
            Log("Connecting to " + $vc.vc)
            $VCconn = Connect-VIServer -Server $vc.vc -Credential $cred -errorAction "Stop"
        } catch [VMware.VimAutomation.ViCore.Types.V1.ErrorHandling.InvalidLogin] {
            Log("Unable to connect to vCentre, invalid logon error !!")
            Log("Abandoning further script processing in order to prevent potential account lockout.")
            Break
        } catch {
            Log("Unable to connect to vCentre - " + $_)
            Continue
        }
     
        # Get ESX objects
        Log("Getting list of ESXs to check on " + ($vc.vc) + "...")
        $ESXs = Get-VMHost -Server $vc.vc | Sort -property Name
        Log("Got list of " + ($ESXs.Count) + " ESXs to check") 
     
        ForEach ($ESX in $ESXs) {
            $row = "" | Select VC, Cluster, Name, IP, Version, Make, Model, BiosVer, CpuCores, CpuModel, HbaModel, HbaDriver, HbaDriverVer, Nic1Model, Nic1Driver, Nic1DriverVer, Nic2Model, Nic2Driver, Nic2DriverVer
            Log($ESX.Name)
     
            # Store objects which get re-used for efficiency
            $ESXview = Get-View -VIObject $ESX
            $VMHostNetworkAdapter = Get-VMHostNetworkAdapter -VMHost $esx 
     
            # Get the basics
            $row.VC = $vc.vc
            $row.Cluster = $ESX.Parent
            $row.Name = $ESX.Name.Split(".")[0]
            $row.IP =  ($VMHostNetworkAdapter | Where {$_.ManagementTrafficEnabled -eq "True" -or $_.DeviceName -like "vswif*" -or $_.Name -eq "vmk0"}).IP
            $row.Version = $ESX.Version + " (" + $ESX.Build + ")"
            $row.Make = $ESX.Manufacturer
            $row.Model = $ESX.Model
     
            # Now onto the more ESX version / hardware specific stuff (new versions of hardware will require further work below)
     
            # BIOS
            if ($ESXView.Hardware.BiosInfo) {     # Works on some systems 
                $row.BiosVer = $ESXview.Hardware.BiosInfo.BiosVersion + " " + $ESXview.Hardware.BiosInfo.ReleaseDate.ToString("yyyy-MM-dd")   # Need date for HP servers as they use same version no for diff versions!
            } else {
                $row.BiosVer = ($ESXview.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like "*BIOS*"}).Name
                $row.BiosVer = ([regex]::Matches($row.BiosVer, "[A-Z]\d{2} 20\d{2}-\d{2}-\d{2}"))[0].Value           # HP regex to extract "A19 2010-09-30" for example
            }
     
            # CPU info
            $row.CpuCores = $ESXview.Hardware.CpuInfo.NumCpuCores.ToString() + " (" + $ESXview.Hardware.CpuPkg.count + "x" + $ESXview.Hardware.CpuPkg[0].ThreadId.count + ")"
            $row.CpuModel = $ESX.ExtensionData.Summary.Hardware.CpuModel
     
            # HBA info (script assumes only one HBA model in use)
            $row.HbaModel = ($ESX.ExtensionData.Config.StorageDevice.HostBusAdapter | Where {$_.Key -like "*FibreChannel*"})[0].Model
            $row.HbaDriver = ($ESX.ExtensionData.Config.StorageDevice.HostBusAdapter | Where {$_.Key -like "*FibreChannel*"})[0].Driver     # Includes version for ESX3
            $row.HbaDriverVer = ($ESXview.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like "*" + $row.HbaDriver + "*"}).Name
            $row.HbaDriverVer = ([regex]::Matches($row.HbaDriverVer, "(\b\d)(.*?)(?=\s)"))[0].Value
     
            # NIC info (script only supports two distinct NIC types)
            $nics = $ESXview.Hardware.PciDevice | Where {$_.ClassId -eq 512} | Select VendorName, DeviceName, Id | Sort-Object -Property DeviceName -Unique
            if ($nics.count) {
                $row.Nic1Model = $nics[0].VendorName + " " + $nics[0].Devicename
                $row.Nic2Model = $nics[1].VendorName + " " + $nics[1].Devicename
     
                # Use PCI ID to match up NIC hardware type with driver name
                $row.Nic1Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics[0].Id}).ExtensionData.Driver
                $row.Nic2Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics[1].Id}).ExtensionData.Driver
     
                $row.Nic1DriverVer = Get-NicDriverVersion $ESXview $row.Nic1Driver
                $row.Nic2DriverVer = Get-NicDriverVersion $ESXview $row.Nic2Driver
             } else {
                # Annoyingly, $nics is not an array if there's only one NIC type, hence seperate handling
                $row.Nic1Model = $nics.VendorName + " " + $nics.Devicename
                $row.Nic1Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics.Id}).ExtensionData.Driver
                $row.Nic1DriverVer = Get-NicDriverVersion $ESXview $row.Nic1Driver
            }
     
            $Results = $Results + $row
        }
        Disconnect-VIServer -Server $VCconn -Confirm:$false
    }
    $Results | Format-Table *
    Log("Writing results to $OutputFile...")
    $Results | Export-Csv -path $OutputFile -NoTypeInformation
     
    Log("All completed")
    Stop-Transcript

    Hi Aldo,.

    As directed by the PM, I sent you, I genericised the script a bit more, it should be easier to use (no need to the Standard.ps1 file).  Similarly the name of your Center virtual servers don't need to be put in a separate file CSV file is

    To avoid having to create credentials files, delete the following lines...

    # Load password credential from encrypted file
    $pass = Get-Content $PassFile | ConvertTo-SecureString
    $user = Get-Content $UserFile
    $cred = New-Object System.Management.Automation.PsCredential($user, $pass)
    

    .. .and replace by (the script will prompt you for the user/pass)...

    $cred = Get-Credential
    

    Hope this gets you operational.

    Note that I found to NIC and driver versions HBA is quite unreliable using this script, that there is a lot of consistency in what is returned by ICM to hardware vendors.  More on the servers I tested with firmware HBA was never available.  A more reliable, but more complex method is to use PowerShell for SSH for your ESX, which has its own problems, but is another approach (when you do audits of system I tend to use both).  See below for more info...

    http://vblog.Strutt.org.UK/2012/04/ESX-HBA-and-NIC-driverfirmware-versions/

    All the best...

    Simon

  • Crashed hard drive and must be replaced

    I have a Compaq Presario CQ60-204NR, which is not quite 2 years old. The hard drive broke down. I would first like to know if you can tell me if this laptop is 32-bit or 64-bit, and which drive hard ability then I replace the damaged with? I don't know what is needed to replace the hard drive. This laptop came with Windows Vista Home Basic Service Pack 1. Thank you. Linda

    Normally, I would ask you if you are running 32 or 64 bit, but according to your specifications you are running 2 GB of RAM, which would indicate that it is 32-bit. It takes at least 3 GB of RAM to run 64-bit.

    You can use almost all SATA 2.5-inch drive in it. The largest capacity as 1 terabyte or more are too thick and doesn't work.

    I'd go for at least 500 GB drive at 7200 RPM / min. Seagate is a nice hybrid drive that is fast enough and is still affordable.

    http://www.Seagate.com/www/en-us/products/laptops/laptop-HDD/

    Install the new drive and use your HP recovery DVD to reinstall your operating system.

    Do you know how to replace a hard drive?

  • Aspire driver E5-571-39EN issues in Win7 x 64

    Hello world

    I'm looking for a solution for my network interface cable and my touchpad works properly.

    The drivers from the site Web has not helped so far, the NIC (Realtek) driver displays an error message during the installation and neither Touchpad driver files two allows me to "click by pressing the touchpad."

    Am I missing something?

    Kind regards

    Wolfgang

    Well,.

    I was sure that I downloaded to Win7, but apparently they were Win8 versions of driver on my computer - sry for this.

  • Driver for Dell Wireless 1505 Draft 802.11n WLAN Mini Card

    Have your Studio 540 desktop provided with Windows VISTA. I then updated to Windows 7 64-bit. The 5G band worked until the death of my old router.

    I bought a new Western Digital N600 dual-band router. The problem I have is that my PC does not record the band of 5G, only 2. 4 g. NIC card driver dates back to 2008 (Dell) and the manufacturer (Broadcom) transmits the responsibility of Dell. Won't even talk about it.

    My iPAD recognizes 5G so I know the router is OK.

    Anyone know how to get the last driver W7 for this card? I don't see how to get it from Dell.

    It is better to just go and buy a new NIC card?

    Thank you, Bob

    Hi Bob,

    Windows 7 drivers for Wireless 1505 Draft 802.11n WLAN Mini: http://dell.to/17ZAD3Q

    Click on the link, select the downloaded file and follow the instructions on the screen to complete the installation.

    Check to see if that helps and response.

  • vmkping cannot send packets larger than 504 bytes? IGB driver broken?

    Hi all

    I have a HP ProLiant DL360e Gen8 with 96 GB RAM Server installed.

    There are 4 1Gbit NIC (igb driver used)

    ~ # esxcfg - NICS - l

    Name PCI Driver link speed Duplex MAC address MTU Description

    vmnic0 0000:02:00.00 igb up to 1000Mbps Full 38:63:bb:2 c: a5:b8 1500 Intel Corporation I350 Gigabit Network Connection

    vmnic1 0000:02:00.01 igb up to 1000Mbps Full 38:63:bb:2 c: a5:b9 9000 Intel Corporation I350 Gigabit Network Connection

    IGB 0000:02:00.02 vmnic2 low 0Mbps half 38:63:bb:2 c: a5:ba 1500 Intel Corporation I350 Gigabit Network Connection

    IGB 0000:02:00.03 vmnic3 low 0Mbps half 38:63:bb:2 c: a5:bb 1500 Intel Corporation I350 Gigabit Network Connection

    ~ #

    I use ESXi 5.5 U2:

    ~ # esxcli get version system

    Product: VMware ESXi

    Version: 5.5.0

    Build: Releasebuild-2718055

    Update: 2

    ~ #

    There are 2 local vSwitches:

    ~ # esxcfg - vswitch - l

    Switch name Num used Ports configured Ports MTU rising ports

    2432 4 128 1500 vmnic0 vSwitch0

    Name PortGroup VLAN ID used rising Ports

    The VM network 0 0 vmnic0

    0 1 vmnic0 Mgmt

    Switch name Num used Ports configured Ports MTU rising ports

    2432 4 128 9000 vmnic1 vSwitch1

    Name PortGroup VLAN ID used rising Ports

    San 1 950 vmnic1

    ~ #

    ~ # esxcfg - vmknic - l

    Port Group/DVPort/Opaque IP IP family network interface address Netmask Broadcast MAC address MTU TSO MSS active Type

    vmk0 mgmt IPv4 192.168.4.232 255.255.255.0 192.168.4.255 38:63:bb:2 c: a5:bb 1500 65535 true STATIC

    vmk1 san IPv4 172.25.50.232 255.255.255.0 172.25.50.255 00:50:56:67:28:d2 9000 65535 true STATIC

    ~ #

    The VMKernel vmk1 interface is configured to connect to the NFS data store (using separate nic vmnic1 and VLANS separated 950). But there was time-out problems when you try to access the NFS datastore.

    What I realized is that I'm not able to ping to NFS datastore (and vice versa) with the larger than 504 bytes... packet size:

    ~ # vmkping - I vmk1 d 172.25.50.233

    PING 172.25.50.233 (172.25.50.233): 56 data bytes

    64 bytes from 172.25.50.233: icmp_seq = 0 ttl = 64 time = 0.296 ms

    64 bytes from 172.25.50.233: icmp_seq = 1 ttl = 64 time = 0,235 ms

    64 bytes from 172.25.50.233: icmp_seq = 2 ttl = 64 time = 0,236 ms

    -172.25.50.233 - ping statistics

    3 packets transmitted, 3 packets received, 0% packet loss

    round-trip min/avg/max = 0.235/0.256/0.296 ms

    ~ # vmkping - I vmk1 s 504 - d 172.25.50.233

    PING 172.25.50.233 (172.25.50.233): 504-data bytes

    512 bytes from 172.25.50.233: icmp_seq = 0 ttl = 64 time = 0,338 ms

    512 bytes from 172.25.50.233: icmp_seq = 1 ttl = 64 time = 0,268 ms

    512 bytes from 172.25.50.233: icmp_seq = 2 ttl = 64 time = 0,234 ms

    -172.25.50.233 - ping statistics

    3 packets transmitted, 3 packets received, 0% packet loss

    round-trip min/avg/max = 0.234/0.280/0.338 ms

    ~ # vmkping - I vmk1 s - 505D 172.25.50.233

    PING 172.25.50.233 (172.25.50.233): 505-data bytes

    -172.25.50.233 - ping statistics

    3 packets transmitted, 0 packets received, 100% packet loss

    ~ #

    What more, I ran pktcap-uw tool to look at packets on a network interface:

    for:
    # vmkping - I-c - 1 d 172.25.50.233 vmk1

    There are visible packages:

    12:17:14.50741 [6] captured at point EtherswitchDispath, TSO do not activated, Checksum not unloaded and not checked, 950, length 98 brand VLAN.

    Segment [0] - 98 bytes:

    0x0000: 0050 5667 28 d 2 0cc4 7a 18 0800 4500 3bd4

    0 x 0010: 0054 1e4e 4000 4001 ac19 32e9 ac19 5e57

    0 x 0020: 32e8 0000 e6af 0000 4699 555d CCCA 0000

    0 x 0030: c58b 0809 0a0b 0c0d 1011 1213 1415 0e0f

    0040: 1617 1819 1a1b 1c1d 1e1f 2021 2223 2425 x 0

    0 x 0050: 2627 2829 2a2b 3031 3233 3435 2e2f 2c2d

    0 x 0060: 3637

    but for:

    # vmkping - I vmk1-c 1 s - 505D 172.25.50.233

    There is nothing visible on the physical interface.

    The package is visible on the layer "vmk1":

    ~ # pktcap - uw - vmk vmk1

    The name of the key vmk is vmk1

    No server specified, port select 39635 as port

    The news of package to the output console.

    CID local 2

    Listen on port 39635

    Accept... Vsock connection port 1028 cid 2

    12:19:52.182469 [1] captured at PortInput point, OSI not activated, not unloaded and not verified Checksum, length 547.

    Segment [0] - 547 bytes:

    0x0000: 0cc4 7a 18 0050 5667 28 2 0800 4500 d 3bd4

    0 x 0010: 0215 1ac7 4000-4001-601 d ac19 32e8 ac19

    0 x 0020: 32e9 0800 0000 555d cd68 0002 de9a b1a5

    0 x 0030: c87a 0809 0a0b 0c0d 1011 1213 1415 0e0f

    0040: 1617 1819 1a1b 1c1d 1e1f 2021 2223 2425 x 0

    0 x 0050: 2627 2829 2a2b 3031 3233 3435 2e2f 2c2d

    0 x 0060: 3637 3839 4041 4243 4445 3e3f 3c3d 3a3b

    0 x 0070: 4647 4849 4a4b 4c4d 5051 5253 5455 4e4f

    0 x 0080: 5657 5859 5a5b 5c5d 6061 6263 6465 5e5f

    0 x 0090: 6667 6869 6a6b 6c6d 6e6f 7071 7273 7475

    0x00a0: 7677 7879 7a7b 7c7d 7e7f 8081 8283 8485

    0x00b0: 8687 8889 8a8b 8c8d 9091 9293 9495 8e8f

    0x00c0: 9697-9899 9a9b 9c9d 9e9f a0a1 a2a3 a4a5

    0x00d0: a6a7 a8a9 aaab acad b0b1 b2b3 b4b5 aeaf

    0x00e0: b6b7 b8b9 bebf c0c1 c4c5 c2c3 CHB babb

    0x00f0: CACB RCC cecf d2d3 d4d5 d0d1 c8c9 c6c7

    0x0100: d6d7 d8d9 David e0e1 e4e5 e2e3 dcdd dadb

    0 x 0110: e6e7 e8e9 eaeb eced eeef f0f1 f2f3 f4f5

    0 x 0120: f6f7 f8f9 with fcfd 0001 0203 0405 feff

    0 x 0130: 0607 0809 0a0b 0c0d 1011 1213 1415 0e0f

    0140: 1617 1819 1a1b 1c1d 1e1f 2021 2223 2425 x 0

    0 x 0150: 2627 2829 2a2b 3031 3233 3435 2e2f 2c2d

    0 x 0160: 3637 3839 4041 4243 4445 3e3f 3c3d 3a3b

    0 x 0170: 4647 4849 4a4b 4c4d 5051 5253 5455 4e4f

    0 x 0180: 5657 5859 5a5b 5c5d 6061 6263 6465 5e5f

    0 x 0190: 6667 6869 6a6b 6c6d 6e6f 7071 7273 7475

    0x01a0: 7677 7879 7a7b 7c7d 7e7f 8081 8283 8485

    0x01b0: 8687 8889 8a8b 8c8d 9091 9293 9495 8e8f

    0x01c0: 9697-9899 9a9b 9c9d 9e9f a0a1 a2a3 a4a5

    0x01d0: a6a7 a8a9 aaab acad b0b1 b2b3 b4b5 aeaf

    0x01e0: b6b7 b8b9 bebf c0c1 c4c5 c2c3 CHB babb

    0x01F0: CACB RCC cecf d2d3 d4d5 d0d1 c8c9 c6c7

    0 x 0200: d6d7 d8d9 David e0e1 e4e5 e2e3 dcdd dadb

    0 x 0210: e6e7 e8e9 eaeb eced eeef f0f1 f2f3 f4f5

    0 x 0220: f8 f6f7

    If I understand correctly, packets are lost somewhere between vmk1 and vmnic1 interfaces?

    I tried to change the interfaces physical, but all the same behavior.

    What is my broken hardware?

    Is the driver of the igb broken?

    See you soon

    Marek

    The problem is resolved.

    The question was in the configuration of switch HP (HP Procurve 2530 - 24g). There was a line in the config:

    back-filter

    After you turn off the back of the filter (# filterless back) all started to work.

    Marek

  • Downgrade from Windows 7 64 for XP 64 bit for the Presario Compaq CQ61 - 319WM VM371UA

    HI - lets get right:

    You have now the Compaq Presario CQ61-319WM in front of you is preloaded with Win7, but you want to downgrade to your copy of XP64bit.

    Your system is:

    AMD Athlon II M300 64-bit multiprocessor Dual Core @ 2 GHz

    RS780/RS880 (M)<- your="" northbridge="">
    ATI Mobility Radeon HD 4200 (3400 variant?)<- your="">
    SB750<- southbridge="">

    1 unit comes with a 250 GB HARD drive. Replace it with another SATA HDD for your copy of xp64 bit before powering it, by registering and activating, seeing that this solution is not yet complete, saving your software Windows 7 preinstalled in this way.

    NOTE: Do not install Windows XP 64 - bit Edition on your current 250GB Win7. If you did get the Compaq CD to restore.

    Download nLite from 2 a. nLiteOS.com to integrate SATA drivers (called: "Slipstream") inside your Windows CD otherwise: BSOD. (recommended method)

    -or-

    2B. After changing BIOS to recognize the floppy USB download drive drivers SATA on diskette and the XP CD, press F6 to manually load these drivers SATA AHCI floppy.

    3. use your Slipstreamed CD and let XP starts normally (no key of F)

    -Si Windows successfully installed continue-

    4. now that XP64 bit runs the first thing that you want to install the .NET Framework 3.0 would be.

    5. install Visual C++ redistributable (free version)

    6 install the network driver. See below

    NOTE: 8102 & 8103 pilots would most likely work, not 8139 family.

    Here is a list of the most easy to install drivers:

    -Agere Systems HDA Modem - SOLVED!

    -Atheros AR9285 WiFi adapter - SOLVED!

    and the most difficult of them...

    -AMD Mobility Radeon HD 4200 shared memory<(unsolved)>

    -IDT High Definition Audio CODEC<(unsolved)>

    -Realtek RTL8139/810 x Fast Ethernet Adapter - SOLVED!

    -AMD AHCI SATA Compatible RAID controller - SOLVED!

    -ATI SM BUS - SOLVED!

    A breakdown of the versions of the driver that is used in our tests:

    ATI SM BUS

    /*
    Description of Driver ATI SMBus
    Date 26/02/2007 driver
    5.10.1000.8 driver version
    Provider of driver ATI Technologies Inc.
    Oem3.inf INF file
    Hardware ID PCI\VEN_1002 & DEV_4385 & SUBSYS_363F103C & REV_3C
    Location Information PCI bus 0, device 20, function 0
    PCI Device ATI SB750 - SMBus Controller
    */

    AMD AHCI COMPATIBLE RAID CONTROLLERS

    /*

    Driver Description AMD AHCI Compatible RAID Controller
    Date of the driver 17/03/2009
    3.1.1540.127 driver version
    Advanced Micro Devices, Inc. driver provider.
    File INF oem0.inf
    Hardware ID PCI\VEN_1002 & DEV_4391 & SUBSYS_363F103C & REV_00
    Location Information PCI bus 0, device 17, function 0
    PCI Device ATI SB750 - SATA AHCI Controller
     
    Device resources
    IRQ 22
    Memory D0408000-D04083FF
    Port 4010-401e
    Port 4030-4037
    4038-403(f) port
    Port 404 B-4048
    Port 404c-404F
    */

    AMD RAID CONSOLE

    /*
    Driver Description AMD RAID Console
    Date of the driver 17/03/2009
    3.1.1540.127 driver version
    Advanced Micro Devices, Inc. driver provider.
    File INF oem0.inf
    Hardware ID SCSI\ProcessorAMD___RAID_Console___1.00
    Place of information Bus number 0, target 10 ID, LUN 0

    */

    ATHEROS AR9285 WIRELESS INTERMEDIATE DRIVER

    /*
    Description of Driver Atheros AR9285 802. 11 b / g WiFi Adapter - wireless driver intermediate
    Date of the driver 16/03/2009
    1.0.0.92 driver version
    Driver WS provider
    Oem8.inf INF file
    Hardware ID wsimdmp

    */

    ATHEROS AR9285 WIRELESS NETWORK ADAPTER

    /*
    Description of Driver Atheros AR9285 802. 11 b / g WiFi adapt
    Date 2009-06-22 driver
    7.7.0.348 driver version
    Driver Atheros vendor
    Oem7.inf INF file
    Hardware ID PCI\VEN_168C & DEV_002B & SUBSYS_303F103C & REV_01
    Location Information PCI bus 2, device 0, function 0
    PCI Device Atheros AR9285 802. 11b / g Wireless Network adapt
     
    Device resources
    IRQ 17
    Memory D0100000-D010FFFF
    */

    REALTEK ETHERNET CARD WIRELESS INTERMEDIATE DRIVER

    /*
    Driver Description Realtek RTL8102E/RTL8103E family PCI-E Fast Ethernet NIC - wireless driver intermediate
    Date of the driver 16/03/2009
    1.0.0.92 driver version
    Driver WS provider
    Oem8.inf INF file
    Hardware ID wsimdmp

    */

    REALTEK ETHERNET CARD DRIVER

    /*
    Driver Description Realtek RTL8102E/RTL8103E family PCI-E Fast Ethernet NIC
    Date 25/09/2008 driver
    5.706.925.2008 driver version
    Driver provider Realtek Semiconductor Corp.
    Oem28.inf INF file
    Hardware ID PCI\VEN_10EC & DEV_8136 & SUBSYS_363F103C & REV_02
    Location Information PCI bus 3, device 0, function 0
    PCI Device Realtek RTL8139/810 x Fast Ethernet Adapter
     
    Device resources
    IRQ 18
    Memory D0000000-D000FFFF
    Memory D0010000-D0010FFF
    Port 2000-20FF

    */

    AGERE SYSTEMS HDA MODEM

    /*

    Driver Description Agere Systems HDA Modem
    Date 21/11/2008 driver
    2.1.92.0 driver version
    Provider of driver Agere
    Oem30.inf INF file
    Hardware ID HDAUDIO\FUNC_02 & VEN_11C1 & DEV_1040 & SUBSYS_103C137E & REV_1002
    Rental Information Bus internal High Definition Audio
    */

    On our test unit CQ61 we currently have ALL but TWO missing drivers. the Audio driver and the video!

    After consultation with AMD, IDT and Insyde each has decided that this problem is with Compaq "Softpaqs Engineering Team", in the meantime a viable solution. Support for Compaq of level 2 has been unable to help in this case, however, agreed to intensify this concern to the "level 3" (genius).

    "Diversity is the key to break the monotony" Obviously, still a challenge for the Presario team in this area.

    Our testing shows that the problem exists in the firmware of the cards mothers; Perhaps the BIOS. Insyde (SSII BIOS) indicated that HP/Compaq has the "sp?.» solution "exe" and refused further assistance because of HP/Compaq contracts. "

    So why Compaq insist on locking/force their users in Windows 7, without other Windows based operating system options for this model and others who are currently in production? We're going to investigate.

    Currently, Windows XP 64-bit Edition is still being supported by Microsoft after January 10, 2010. So why not HP?

    Finally.

    Here we have the more stable driver, for most official, complete the value for the model CQ61 running XP64 (and possibly XP as well). It concerns all the drivers listed below:

    Driver SATA AHCI-

    Bus - SM

    -Realtek Ethernet Controller

    -ATI Mobility Radeon HD 4200 video driver

    Driver Modem Agere-

    -Atheros WiFi driver

    Use this forum as the timestamp.

    There were too many sources to the list for the updated driver, so a full driver package was created in place to keep things simple, without all the headaches of doing it yourself.

    This package should work on XP 64-bit operating systems based and is released as is. The instructions are inside each directory.

    NOTE: After downloading Please run the 1st prerequisites folder, then all other folders depending on numbers starting with 1 ( 0 record is for your slipstream). Here are the details of the file:

    Compaq CQ61-319WM Presario VM319WM Driver for XP64bit.7z

    MD5 Checksum = 7AAA90D0C06778630CF1117CEB318974 MD5 download www. MD5summer.org /

    As always with any software Please check against your trust of anti-virus software on a clean system.

    You will need 7zip, which can be downloaded from www. 7-zip.org in order to extract its contents.

    Download here.

    Last NOTE: If MD5 checksums do not match after downloading, remove it immediately. In this community, we are here to assist you in all possible ways to make your life a little easier with the PC. This is an ongoing process and the development of this package has been a joint effort from many sources. However, we remain optimistic for the official drivers of HP if they also, we support the cause as highlighted in their slogans and advertising. All in all societies can only works in their resources when it comes to projects like this however... "Diversity is the key to break the monotony", that's why we all think alike. We will stay hopeful. Thank you for your support. * UART *.

  • vNIC: activate the failover or group?

    Hello

    I have a UCS 6248 FI + IOM 2204 + Server B200M3 with:

    -Mezz Slot: empty

    -slot mLOM: VIC 1280

    So I, for the B200M3, 2 x path of 10Gbps of VIC at FI6248:

    -port0, 2204-A, FI - has

    -port1, 2204-B, FI - B

    What is the best practice to configure the veth under UCSManager:

    -use the vNIC 0 (fabric) + activate failover: with this choice, I use only 1 x 10 gb/s (for ethernet) path; the path through fabric B would be used, if any device failed on A fabric. In my mind, it is not the best way to use the architecture of the UCS.

    -use 2 vNIC: vNIC vNIC 1 (plate B) and 0 (fabric): with this choice, the operating system will see the 2 NIC in my case, the OS is W2K8R2: how to set up the consolidation of NETWORK cards?

    -Another idea?

    Many thanks for your advice.

    Best regards.

    Nicolas

    For the Cisco VIC, we have windows 2008 nic teaming drivers.

    Download and install the drivers for Cisco UCS VIC

    Install the NIC Teaming driver

    http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/vic_drivers/install/Windows/2.0/b_Cisco_VIC_Drivers_for_Windows_Installation_Guide_chapter_010.html#d107e478a1635

    Here's another thread on the subject.

    Windows team driver available for M81KR / P81E VIC

    https://supportforums.Cisco.com/message/3592963#3592963

  • Connection WiFi on Windows 7

    I am system administrator for a network that has Windows XP, Windows Vista and Windows 7, the Internet worked very well for everyone until 3 days ago 3 computers that have windows 7 and connect wirelessly to the router stopped having internet connection.

    If you do ipconfig/all, you can see the network card with an IP address, default gateway, and DNS servers, but for some reason it cannot go beyond the router. I ping the router but I can't go furter. All computers on the LAN have no problem. I updated the NIC, unchecked driver for wireless to save energy, I manually added the DNS servers. Nothing seems to work. Is there a solution for this?

    Hello
     
    Are the computers on a domain?

    The question you posted would be better suited to the Technet community. Please visit the link below to find a community that will provide the best support.

     
     
  • Windows search problem

    Hello again!

    With the Windows Start menu, research is pretty easy. But, however, I am facing problem in research. I have to enter the whole word for this thing to appear in the result of the search. Why type the whole word when you can get with just a few letters? Please help me

    Hello rap.

    Thank you for the update on the issue.

    I appreciate your efforts.

    What is the brand and model of your computer?

    I hope that the issue of Windows search is not persistent.

    However, for the network problem, I suggest you uninstall and reinstall the network adapter driver and check if that helps.

    Step 1:
    NIC Uninstall driver. Please follow these steps:

    a. press Windows + X keys and click on Device Manager.
    b. Click to enlarge network adapters.
    c. right click the adapter, then click on Uninstall.

    Step 2:
    The website of the manufacturer of the computer REINSTALL NIC driver and check.
    Reference:
    Download and install the drivers
    http://Windows.Microsoft.com/en-us/Windows-8/all-drivers

    I hope this helps.

    Thank you

Maybe you are looking for