2 wired network adapters on 1 computer

I have 2 wired network adapters on 1 computer (windows XP sp3). I used to use on board one, but now I want to use the plugged in one. The problem is I don't know how to use it because windows doesn't automatically change to it. Could you show me how to do
this?
In additional, I want to connect this computer to the other one using the plugged in adapter, and the other computer will connect directly to the internet. Can I do this and how?
Thanks & Best Regards,
Pham Thanh Long

Switching between the two should be fairly straight forward, assuming Windows has both adaptors detected and installed obviously. Down by the clock, right click on the network icon and select Open Network Connections (if that's not visible, go to Start,
Control Panel, make sure you're in classic view mode, then open Network Connections). Confirm that both adaptors are listed.
Right click on the currently used adaptor and go into Properties, then select "Internet Protocol (TCP/IP)". If the IP and DNS settings are set to obtain them automatically then that's simple, if they're statically assigned then make a note of the settings
and come out of there. Right click on the adaptor and select Disable. Now right click on the adaptor you want to use and if Enable is listed then click it. Go into the properties of this adaptor and set the IP and DNS address details to the same as they were
on the other adaptor, and close those windows. Now, if you move the network cable from the onboard network connection to the other one you should find that Windows starts to use that one.
In terms of connecting to the other machine, I assume you mean using the onboard adaptor that is now unused? That's possible but a little more tricky. You could connect direct between that adaptor and another computer (though if you're going direct rather
than via a switch/hub then you need to use a crossover cable not a normal network cable). You'll need to setup the network IP address details on this adaptor, and they must be on a different network range to the one you've just configured for your main
network. The two machines can now talk to each other using that adaptor.
If you want to be able to access the internet via that second computer (note, you can't have internet access via the other computer AND the normal network since only one adaptor can be configured with a gateway address) then you'd need to configure
Internet Connection Sharing on the other computer as described here
http://support.microsoft.com/kb/306126

Similar Messages

Looking for a way to determine wich Network adapters are truly Wired ethernet.

I'm Working on a little app that is going to validate that the machine is connected to a wired network before we allow it to start a re-installation of the operating system. Our wireless net works great for installed systems (they do have a machine certificate)
but we cannot install on it (since the machine must be domain joined to get that cert)
So far I have not found any method that truly tells if the card is a wired network adapter.
Win32_NetworkAdapter:s AdapterTypeID does not work since many wireless adapters report type=0 wich should be wired adapters.
MSNdis_PhysicalMediumType does not work. It returns undefined for a number of adapters
Many posts on the net talks about detecting the connection state wich doesn't work either since it will return the same value for a connected wired adapter and a connected wireless adapter
Other posts suggests using powershell and looking at tha dapter name. That doesn't work if you
got to support a number of languages and what happends if a user renames the interface?
The only way I can make it sort of work is to pipe the output from netsh LAN show interfaces and then do queries on those adapters but I would prefer a soloution in Code.
Since Netsh can do it, there must be a way to do this

The reason for the C code not running under WinPE was user error ........
Forgot to link it static.
I have been digging around some more and so far the only API that will give us the correct and complete picture seems to be GetIfEntry2, however I can't find dotnet code for it.
It seems like most other methods uses the older GetIfEntry under the hood and that will not give us the true data since many types will report as NDisPhysicalMediumType 0.
However a combination of Win32_network adapter and MSNdis_PhysicalMediumType actually seems to work.
Win32_network filtered on AdapterType='Ethernet 802.3' gives us everything that claims to be an ethernetadapter. That list will however include wireless, bluetooth and some virtual adapters.
MSNdis_PhysicalMediumType filtered on NDisPhysicalMediumType 0 does not show Wireless or Bluetooth but will instead show isatap interfaces and so on.
The Key was to "join" these two on win32_networkadapter.Name to MSNdis_PhysicalMediumType.Instancename giving us the possibility to filter out the unwanted adapters using both methods.
I have made a demoscript that became embarrassing short
'* ListPhysicalAdapters.vbs
'* Purpose : A script to list the true Physical Ethernet adapers.
'* Created : 2005-02-17
Dim colItems_Win32_NetworkAdapter, Colitems_MSNdis_PhysicalMediumType
Dim objNetworkAdapter,objPhysicalMediumType
' Select the adapters that claims to be 802.3 aka ethernet adapters. This will hoverver get anything calling itself an Ethernet adapter
Set colItems_Win32_NetworkAdapter = GetObject("winmgmts:\\.\root\cimv2").ExecQuery("Select * from Win32_NetworkAdapter where AdapterType='Ethernet 802.3'",,48)
For Each objNetworkAdapter in colItems_Win32_NetworkAdapter
' Select the adapters that claimed to be Ethernet Adapters above and filter out the ones who doesn't have an Ethernet Connector (type=0 is used for fallback/undefined)
Set Colitems_MSNdis_PhysicalMediumType = GetObject("winmgmts:\\.\root\WMI").ExecQuery("SELECT * FROM MSNdis_PhysicalMediumType where InstanceName='" & objNetworkAdapter.Name & "' AND (NdisPhysicalMediumType=0 OR NdisPhysicalMediumType=14)",,0)
For Each objPhysicalMediumType in Colitems_MSNdis_PhysicalMediumType
Wscript.Echo "AdapterType: " & objNetworkAdapter.AdapterType & ""
Wscript.Echo "MACAddress: " & objNetworkAdapter.MACAddress
Wscript.Echo "Name: " & objNetworkAdapter.Name
Wscript.Echo "PhysicalMediumType: " & objPhysicalMediumType.NdisPhysicalMediumType
Wscript.Echo ""
next
Next

Cannot log into T61 from remote computer with wired network and Windows Explorer.

Hi,
I am using a T61 7662-cto with Windows 7 Professional
When the T61 is connected on the home network with the wired network, I am not able to log into it remotely from another computer. On my second computer, I see the T61 with Windows Explorer but instead of getting the login window, it appears a Network Error with the message:
“Check the spelling of the name. Otherwise, there might be a problem with your network.” With a error code 0x80070035, “The network path was not found.” I tried the “Diagnose” button but it doesn’t give solution.
When the T61 is wireless connected, there is no problem. I can access it from my second computer.
I never have problem to connect to the second computer from the T61 with any connection type . I just updated the Intel Wireless LAN (bg, abg, abgn) for Windows 7 – ThinkPad, with the drivers required but it changes nothing.
http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-73611
Do you have a hint for this issue why the wired network gives problem?
Thanks

Open this post, go to the flagged message. On its right is a button
to turn off the flag.
I went to the site. The only problem I had was one has to sign in
to see anything. Even the main page had a very large ''Please
Sign In'' covering the window.
Many site issues can be caused by corrupt cookies or cache.
* Clear the Cache and
* Remove Cookies<br> '''''Warning ! ! '' This will log you out of sites you're logged in to.'''
Type '''about:preferences'''<Enter> in the address bar.
* '''Cookies;''' Select '''Privacy.''' Under '''History,''' select Firefox will '''Use Custom Settings.''' Press the button on the right side called '''Show Cookies.''' Use the search bar to look for the site. Note; There may be more than one entry. Remove '''All''' of them.
* '''Cache;''' Select '''Advanced > Network.''' Across from '''Cached Web Content,''' Press '''Clear Now.'''
If there is still a problem,
'''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode]''' {web link}
While you are in safe mode;
Type '''about:preferences#advanced'''<Enter> in the address bar.
Under '''Advanced,''' Select '''General.'''
Look for and turn off '''Use Hardware Acceleration'''.
Poke around safe web sites. Are there any problems?
Then restart.

Installing wireless printer on a computer w/ wired network connection

I'm new to arch and have not found my exact problem in the wiki. I have the system installed and am trying to setup my wireless printer. My computer is connected to a broadband router by cable. I have a wireless router which is also connected to the broadband router so that my wife can have internet access on her laptop downstairs and so that I can print to my wireless printer across the room. The wireless router has WEP security and an SSID of "Moak Home" - I can't figure out how to pass cups the SSID, the WEP password, and the ip address of the printer. The printer is an HP Officejet and was detected by Ubuntu on another system and worked so I know the printer is linux compatible. I have installed hplip along with cups, ghostscript, and gutenprint and have tried setting up the printer via the cups web portal and also by using the gnome printer configuration tool. any help would be greatly appreciated. However, I will be watching the Saints/Falcons game shortly and may not get back here until tomorrow:). I lived in New Orleans for 30 years and cannot help myself.
Last edited by dlmoak (2009-11-03 00:34:26)

Nevertheless, just an ip address doesn't work. Perhaps I don't actually have a network set up. On my Ubuntu computer I can install the printer by providing the ip, the SSID and the wep password to the wireless router. My wife can connect her Windows laptop to the internet by providing the SSID and the wep password to the wireless router. However, her machine and mine are not networked together. Do I need to setup a network consisting of my computer and the printer? I may just not adequately understand the process.

MBP takes long time to restore wired network connection after wake-up

Hello...
My Mid-2010 MBP (MacBookPro6,2) has been experiencing this problem recently -- Whenever I wake up the computer from sleep, it needs approximately 10 seconds to restore its wired network connection. I know there are other annoying connection issues with MBP's WiFi/AirPort out there, but I'm talking about the wired connection here.
Maybe some don't even think this slowness is a problem at all, but this laptop used to be network-ready right after wake-up until 3~4 months ago. That was around the time when I upgraded to SSD and changed some settings via pmset, not sure if that's the culprit. It is now running OS X 10.8.5 and its pmset settings are:
Battery Power:
lidwake              1
ttyskeepawake        1
hibernatemode        3
gpuswitch            2
hibernatefile        /var/vm/sleepimage
displaysleep         2
sleep                15
acwake               0
halfdim              1
sms                  0
lessbright           1
disksleep            10
AC Power:
lidwake              1
ttyskeepawake        1
hibernatemode        0
gpuswitch            2
hibernatefile        /var/vm/sleepimage
womp                 1
displaysleep         10
networkoversleep     0
sleep                60
acwake               0
halfdim              1
sms                  0
disksleep            0
I'd appreciate help of any kind
Thanks,
zuoy

Maybe try this, i am not sure that it will resolve the problem, but it is worth trying anyways.
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/eef49e64-157c-4082-8e80-52e48309691f
Hi All,
I've seen this problem multiple times, especially with Windows 7 64-bit versions and Enterprise edition. The source of the problem appears to be the Bonjour service that is installed in the background and set to "Automatic" when installing certain 3rd
party applications. Apple applications like iTunes and Adobe applications like Acrobat Professional and Creative Suites have been known to cause this problem. I've also seen virtualization software like VMWare and VirtualBox cause similar issues
with network adapters.
The solution in most of the cases I've come across has been to stop and disable the Bonjour service. The Bonjour service also masquerades as a service with a name of the format "##Id_String1.6844F930_blahblahblah". Here's how to disable this service
in Windows 7:
Right-Click on Computer > Select 'Manage'
Expand the 'Services and Applications' section in the bottom of the Left-Nav dialog and Select 'Services'
Sort the Services list by name and look for either "Bonjour" or the "##Id_String..." name mentioned above
Right-Click on the service and select 'Properties'
Click the 'Stop' button to stop the service
Select 'Disabled' from the 'Startup type' drop down list
Click 'Apply' and then 'OK'
Reboot your machine and see if the "Multiple Networks" issue is resolved. If so, you should have internet connectivity again.
Hope this helps.
cheers,
Aaron

How can I use PowerShell to Remove "Ghost" (Old Hidden) VMware Network Adapters in Windows 7?

We recently upgrade the virtual hardware of some of our VMware VM's running Windows 7. One side-effect is that in Windows on these machines, an instance of the NIC from the previous version of virtual hardware remains, as a hidden
device. This can be easily found manually on a machine by enabling Device manager to show hidden devices (registry and a menu option - View...Show Hidden Devices). You can then just right-click on the device in question and uninstall.
The problem here, like in so many other tasks, is that you may have multiple instances, on multiple machines. We had just that, and in scouring the internet for a PowerShell only script to resolve the issue, I could not find one. Therefore, I've written
my own.
This exact script is only seeking out VMware "VMXNET3" nic cards, but could be easily adapted to find Ghost NIC's for a different vendor using my example. There are also some commented lines left in to aid you as an example of how you can
test the various queries in your own environment, on a test machine, before a full-blown deployment.
NOTE: Please try this out (at your own risk - I am not responsible for how this works out for you), and please vote for my answer to this dilemma if this helped you. I'd appreciate it after all of the sweat the script took to crank out.
Thanks!
P.S. This script, of course, requires that Powershell is installed and enabled on the target computer. It then must be run as System - In our environment it is being remotely pushed through a software delivery systems, which runs this scrpt
as system.
THE SCRIPT:
CLS
#Querying WMI for Ghost NICs and Returning Criteria...
Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
Write-Host ""
Write-Host "Checking Powershell Version" -Foreground Yellow
$host.version
Write-Host ""
Write-Host "Searching for Ghost NIC's" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
  Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
  Write-Host ""
  else
  Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
  Write-Host ""
  EXIT 0
#Using Criteria to Obtain the GUID of each Ghost NIC
Write-Host "Getting NIC Variables" -Foreground Yellow
foreach ($_ in $Ghosts) {
  $DID = $_.DeviceID
  If ($DID -NE $NULL)
  Write-Host "The NIC DID: $DID"
  else
  Write-Host "$DID is NULL - Exiting..."
  EXIT 666
  if($DID -NOTLIKE "1*")
   Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
   Write-Host ""
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000$DID"
  ELSE
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00$DID"
  $GUID = $NICREG.NetCfgInstanceId
  Write-Host "The NIC GUID: $GUID"
                $PNPDID = $NICREG.DeviceInstanceID
  $PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
  Write-Host "The truncated PNPDevice ID is $PNPDID"
  Write-Host ""
  Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
  $NICREGPATH = @(1..50)
  foreach ($_ in $NICREGPATH)
   $TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
   if($TESTREG -EQ $FALSE)
    #Write-Host ""
    #Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED
    ELSE
    #Write-Host "True - NIC $_ Exists" -Foreground Green
    $NICID = $_
    $SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath1"
    $SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath2"
    $NICProperties = Get-ItemProperty $SubPath1
    #$NICProperties
    $Match = $NICProperties.ServiceName
    #$Match
    foreach ($_ in $Match) {
    #Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
    #Write-Host ""
    if($_ -NE $GUID)
    #Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
                               #Write-Host ""
    ELSE
    Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
    Remove-Item $SubPath1 -Recurse -ErrorAction SilentlyContinue
    Remove-Item $SubPath2 -Recurse -ErrorAction SilentlyContinue
    $CCS = @("ControlSet001", "ControlSet002")
    foreach ($_ in $CCS) {
     $CCS = $_
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
                                         if($DID -NOTLIKE
"1*")
              $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
                         Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
       ELSE
       $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
       Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
#This is our Success check at the end
Write-Host ""
Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
          $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
  If ($Ghosts -NE $NULL)
  Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
  Write-Host ""
  EXIT 666
  else
  Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
  Write-Host ""
  EXIT 0

THE SCRIPT:
CLS
#Querying WMI for Ghost NICs and Returning Criteria...
Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
Write-Host ""
Write-Host "Checking Powershell Version" -Foreground Yellow
$host.version
Write-Host ""
Write-Host "Searching for Ghost NIC's" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
Write-Host ""
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0
#Using Criteria to Obtain the GUID of each Ghost NIC
Write-Host "Getting NIC Variables" -Foreground Yellow
foreach ($_ in $Ghosts) {
$DID = $_.DeviceID
If ($DID -NE $NULL)
Write-Host "The NIC DID: $DID"
else
Write-Host "$DID is NULL - Exiting..."
EXIT 666
if($DID -NOTLIKE "1*")
   Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
   Write-Host ""
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000$DID"
ELSE
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00$DID"
$GUID = $NICREG.NetCfgInstanceId
Write-Host "The NIC GUID: $GUID"
                $PNPDID = $NICREG.DeviceInstanceID
$PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
Write-Host "The truncated PNPDevice ID is $PNPDID"
Write-Host ""
Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
$NICREGPATH = @(1..50)
foreach ($_ in $NICREGPATH)
   $TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
   if($TESTREG -EQ $FALSE)
    #Write-Host ""
    #Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED
    ELSE
    #Write-Host "True - NIC $_ Exists" -Foreground Green
    $NICID = $_
    $SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath1"
    $SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath2"
    $NICProperties = Get-ItemProperty $SubPath1
    #$NICProperties
    $Match = $NICProperties.ServiceName
    #$Match
    foreach ($_ in $Match) {
    #Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
    #Write-Host ""
    if($_ -NE $GUID)
    #Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
                                #Write-Host ""
    ELSE
    Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
    Remove-Item $SubPath1 -Recurse -ErrorAction SilentlyContinue
    Remove-Item $SubPath2 -Recurse -ErrorAction SilentlyContinue
    $CCS = @("ControlSet001", "ControlSet002")
    foreach ($_ in $CCS) {
     $CCS = $_
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
                                         if($DID -NOTLIKE
"1*")
              $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
                         Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
       ELSE
       $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
       Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
#This is our Success check at the end
Write-Host ""
Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
          $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
Write-Host ""
EXIT 666
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0
Hello Octavio,
I'm having similar issues with azure VMs (windows server 2008 and 2012). I noticed that the name of the network adapter changes every time the servers are turned off and then on.
For example every time I perform that action on each VM, the network adapter became to "Microsoft Hyper-V Network Adapter #3" (and then #4, #5, etc).
I found in to many forums that to resolve that is needed to remove Hidden (Ghost) Network Adapters and most of the people is doing that manually from the device manager (right click on the hidden network adapter and select uninstall).
Then I found this script created by you and made some changes to find Description -like "Microsoft Hyper-V Network*".
It seems to find the adapters and also remove them (based on the script results). But if I go to the device manager after restarting the server, all hidden (ghost) adapters are still there (for example Microsoft Hyper-V Network Adapter
#2, Microsoft Hyper-V Network Adapter #3, Microsoft Hyper-V Network Adapter #4, Microsoft Hyper-V Network Adapter #n).
The only thing I noticed after running the script is that, in the Control Panel -> Network and Sharing Center, the name of the adapter has no # (Now is shown as “Ethernet” and before as “Ethernet #”)
This is my script, could you please take a look and tell me if there is something wrong o missing?
CLS
#Querying WMI for Ghost NICs and Returning Criteria...
Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
Write-Host ""
Write-Host "Checking Powershell Version" -Foreground Yellow
$host.version
Write-Host ""
Write-Host "Searching for Ghost NIC's" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "Microsoft Hyper-V Network*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
Write-Host ""
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0
#Using Criteria to Obtain the GUID of each Ghost NIC
Write-Host "Getting NIC Variables" -Foreground Yellow
foreach ($_ in $Ghosts) {
$DID = $_.DeviceID
If ($DID -NE $NULL)
Write-Host "The NIC DID: $DID"
else
Write-Host "$DID is NULL - Exiting..."
EXIT 666
if($DID -NOTLIKE "1*")
Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
Write-Host ""
$NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\000$DID"
ELSE
$NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\00$DID"
$GUID = $NICREG.NetCfgInstanceId
Write-Host "The NIC GUID: $GUID"
$PNPDID = $NICREG.DeviceInstanceID
$PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
Write-Host "The truncated PNPDevice ID is $PNPDID"
Write-Host ""
Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
$NICREGPATH = @(1..50)
foreach ($_ in $NICREGPATH)
$TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
if($TESTREG -EQ $FALSE)
#Write-Host ""
#Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED
ELSE
#Write-Host "True - NIC $_ Exists" -Foreground Green
$NICID = $_
$SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
#Write-Host "The Sub-Key Path To Query = $SubPath1"
$SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
#Write-Host "The Sub-Key Path To Query = $SubPath2"
$NICProperties = Get-ItemProperty $SubPath1
#$NICProperties
$Match = $NICProperties.ServiceName
#$Match
foreach ($_ in $Match) {
#Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
#Write-Host ""
if($_ -NE $GUID)
#Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
#Write-Host ""
ELSE
Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
Remove-Item $SubPath1 -Recurse -ErrorAction SilentlyContinue
Remove-Item $SubPath2 -Recurse -ErrorAction SilentlyContinue
$CCS = @("ControlSet001", "ControlSet002")
foreach ($_ in $CCS) {
$CCS = $_
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
if($DID -NOTLIKE "1*")
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
ELSE
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
#This is our Success check at the end
Write-Host ""
Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "Microsoft Hyper-V Network*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
Write-Host ""
EXIT 666
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0

Can't reinstall Officejet Pro 8000 A809N driver on wired network

Computer is running Windows XP with service pack 3 and all updates installed. When I tried to print two days ago, I received an error message that no printer was installed. I had printed earlier in the week without problems. I checked the Printer and Faxes folder in Control Panel, and it was empty. I believe it normally showed the HP printer as well as a Windows Fax print-to-file routine there.
When I clicked on Add a Printer in the Printer folder, I was told that the Print Spooler was not running. I ran "services.msc" from the Run command, and restarted the Print Spooler. I went back to the Printer folder, tried to reinstall the printer, and again it said the Print Spooler was not running. I restarted the Print Spooler again, and tried to look at Server Properties from the Printer folder file tab, and again it said the Print Spooler was not running (it is set to automatic restart). I've checked several related dll and exe files against their backups, and they don't appear to be corrupted. I scanned the hard drive for errors, and none were found.
I tried the built-in diagnostics of the HP software, and all I got was error messages that the Print Spooler was stopped. I came to the HP website, downloaded and installed two additional troubleshooting programs, which did not help. HP Home Network Diagnostic Utility says "software not installed", although nothing had been deleted, and still ran from the Start menu. HP Print Diagnostic Utility 4.1 states there is an issue with the print spooler, and to click "Fix". Clicking Fix opens a window stating to select the printer to troubleshoot, then press "Diagnose". No printer appears in the list though, so it states to install the software.
Therefore, I downloaded both the full and the limited install programs from the website and tried both several times. I ran the uninstall program of the existing installation from the Start menu without problems and rebooted. When I tried to reinstall though, I kept getting errors. Generally, the "hpnwchk" program (HP network check) opens in a dos screen, displays a long string of "Printer : (null)" lines, then crashes. The program then tells me that the printer is already installed to the TCP/IP port, and needs to be removed first. I click the option to "Fix" the TCP/IP port option. The installation program then continues, and brings up a window showing the correct information for my printer (it even wakes it from the standby mode). I select the printer from the list, and the install continues until receiving another error, stating that "arguments are incorrect", and that the installation has failed. I think the "arguments" are setting for the TCP/IP port, which differ between what it is being set from the current drivers and what was previously installed.
I've run the uninstall routine several times, and also manually deleted the printer folder from the registry using REGEDIT (HKCU/Printer). It seems to me that there is a conflict somewhere that keeps stopping the print spooler (it is set to auto restart). Also, the uninstall routine is not completely uninstalling, as it always says that the printer is already installed when I run the installation routines, and displays it's correct parameters. I Googled and read just about everything I can find on the subject, and I'm stumped. Where else could the TCP/IP settings be stored in the Registry, and what else is being missed on the uninstall?
Some additional information on my setup - the printer has been installed for about 2 years with no issues. I can still print without problems from another computer on our home wired network. I opened Vista on this very computer on a separate drive partition, and had no trouble installing and using the printer through Vista, which seems to eliminate any possible hardware issues (I never found it worth the effort to move over to Vista after trying it; only use it now as a back-up to XP on the computer). In the past week, I installed an update for Adobe Reader, and Microsoft Security Essentials stopped a Java Script Trojan. I believe Windows also installed it's monthly anti-virus update. All virus scans have been negative. Beyond that, there has been no other hardware or software changes.
This question was solved.
View Solution.

I found a solution to the problem, through early morning inspiration. I thought as everything disappeared from the Printer folder, and kept being told that the printer was installed, that I would delete and reinstall other drivers that may (or may not) have been in the folder. I seemed to recall that I had the generic Fax driver installed, and the Microsoft XPS Document Writer installed. I went to "Add/Remove Windows Components", and deleted Fax Services. I then went to the Printer file, clicked Add a Printer, and didn't receive the error message that the Print Spooler wasn't running, ect. I then had no problem reinstalling the HP printer, Fax, and XPS drivers.

Airport Extreme wired network can't assign IP address, but wireless works

*Problem details:*
We have three computers intermittently on, wired into the ethernet LAN managed by the Airport Extreme.
We have a few more computers that connect to the wireless network managed by the same Airport Extreme.
As far as I know, no fancy settings hijinks have been attempted. I manage the router, and I only plugged the Airport into the cable modem and connected all the wires to the computers. The WiFi setup went a similar way -- I just turned it on and it sorted itself out. This was eight months ago, mind you -- everything has been going quite well up until this weekend.
But! I got home from a trip this weekend to discover that all the machines that connected over the wired network could no longer get a connection to the internet. Any machine connected over the wireless network, however, was working just fine. Indeed, my macbook pros couldn't even see the Airport Extreme when I turned off their WiFi, connected them over Ethernet and opened the Airport Extreme configuration app!
The wired machines complain that they have a self-assigned IP address. Sometimes, after resetting everything, they look like everything's fine for a moment. Like I said, ordinarily my macbook pro does not even recognize the router over the wired network. However, after reverting to factory defaults and restarting the Airport, the laptop did see it (until a few minutes went by and it realized something was wrong).
I figured that renewing my DHCP lease would fix this problem, but it did not. Nor did turning off Passive FTP Mode (PASV) under Proxies in the Network configuration pane.
I have tried resetting the router to factory defaults, power cycling the modem and router in various configurations, etc. but nothing has worked. In addition, I have verified that connecting any machine to the ethernet directly from the modem will work, so the problem is definitely being introduced by the Airport Extreme.
So I guess my question is: what do I have to poke to return everything to normal? I'd like working wired and wireless networks again.
*Some last few details:*
The Airport is running 7.5.2, but downgrading to 7.4.2 produced no tangible difference.
I have an Ubee D3.0 modem. All lights are green and blinky except the DS light, which is solid amber (and it is green when the modem is wired directly to one of my computers -- it's only amber when connected to the Airport).
Some of the machines that can't connect to the wired network are PCs, so it's not just an OSX thing.
My roommate's XBOX 360 can connect to the internet over the wired port. It doesn't have WiFi, so I'm pretty sure there's no way it could be fooling me.
Thanks in advance for any advice you can muster.
EDIT FOR APOLOGIES:
I didn't realize I was posting this in the "Airport for Windows" section. While a Windows computer's connection is a concern, I would much rather get my Macs online and deal with that first. I can't figure out how to move the message myself.

*An update:*
Several days later, this issue seems to have fixed itself. I suspect there may have been Funny Business on my ISP's end (but then again, it's an ISP).

HP LaserJet Pro m201dw suddenly not printing via ethernet (wired) network using Mac OS 10.10.1

Hi,
My brand-new HP LaserJet Pro M201dw is suddenly not cooperating when I go to print using my Mac. I had it set up following the directions which closest matched my OS and it worked perfectly for one week; today suddenly it won't cooperate. The printer is seen on the network. I have deleted and re-installed it from my System Preferences several times. I have rebooted my computer. I cannot seem to get it to work. Even the HP Utility is having difficulty. The HP Utility is suddenly slow and often needs to be force-quit as it hangs when I navigate to other applications (web browser, etc.) while waiting for it to respond to clicks. Most often the HP Utility shows the printer in the status ara as "Device Status: Unknown" and "Supplies: Unknown" which it wasn't having issues with yesterday.
Can anyone help me troubleshoot this device? Is there better documentation than the basic setup page here on HP? What about adjusting some setting in the printer web page (which I can access) - is the answer in there?
Thank you.

Hi @td2243,
I see that you are having issues printing over the wired network. I would like to help you out with this issue today.
Try and ping the printer.
On the Apple menu bar, click Go, then click Applications, then Network Utilities. (you can go to the finder and type in Network Utilities)
Click on PING from the bar at the top of the window.
Enter the IP Address of the printer and click Ping.
Did you get any replies back?
Repair the Disk Permissions on the Mac:
Close all applications.
On the Apple menu bar, click Go, click Applications and then click Utilities.
Double-click Disk Utility.
Highlight your hard drive/partition on the left.
Click Verify and then Repair Disk Permissions.
Restart the computer..
Reset the Printing System:
Note: This will remove all printers in the print and Fax/Scan, any printer removed can be re-added later by clicking the plus (+) symbol.
Click the Apple icon and then click System Preferences.
Click Printers & Scanners.
Right-click (or Ctrl +click) in the left white side panel, then click Reset printing system.
Click OK to confirm the reset.
Type the correct Name and Password.
Click OK to reset the printing system.
Then click the + sign to add the driver, highlight the printer. (you might have to click the drop down to select the printer's name) Then click on the Add button.
Try printing again.
Here is some more information on this issue.
A 'Network Product(s) Not Found' Error Displays for the HP LaserJet Pro M201 and M202 Printer Series...
How is the printer name listed in Printers and Scanners? You may provide screen shots if you like.
If you need further assistance, just let me know.
Have a nice day!
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

Wired Network conputer cannot find host printer

I cannot print to host printer on a home wired network.
Printer is HP Photosmart 7520 e all in one.
Host Compter is a Dell Dimension 8100
Pentium 4 1.3 GHz 2.0 GB RAM
Windows XP SP3 host computer.
Netgear N600 Dual Band Router
Model WNDR3400
Network Computer:
Nobilis
Pentium 4 dual core 2.8 GHz
2.5 GB RAM
Linux Mint 17 OS
Both computers share the internet without any problems. The Dell computer prints without any problems. The Dell computer properties 'share this printer' box is checked. I cannot find any IP address for the printer. When I printed out the printer configuration sheet, no IP address was given. When I go to the Control Center->Printers->local-host on the Linux OS, it says it is 'connected to local-host' and 'There are no pinters configured yet'. I then selected 'Add' to add a printer. A 'New Printer' screen comes up and ask to 'Select Device' and also 'Enter URI'. This is where I am stopped in my tracks since I have no 'URI'. Under the 'select device' side there are several options: LPT #1, Serial Port #1, Enter URI, and 'Network Printer'. If Network Printer is selected a dropdown list appears: The main heading is "Find Network Printer'. Selecting 'Find Network Printer' gives various internet protocols (ipp, ipps, https, ipp14, LPD/LPR Host or Printer, Windows printer via Samba, and APP Socket/HP Direct.
The Dell computer has alway worked fine and without problems (XP OS) on any HP printer.
This is where I am stymied! Can someone help me from here.

Can you see the Windows computers when browsing from GO > Connect to server?
Anything different in network connection - you use wireless, they use ethernet, for example?

Intermittent wired network connection on HP OfficeJet Pro 8600

I've searched the forums and I haven't seen a problem/solution quite like I am experiencing, so I am starting a new thread.
I have a HP OfficeJet Pro 8600 that will only keep an intermittent connection to my router. Lately, it has been more often not than connected. I usually have to disconnect and connect the Ethernet cable to the back of the printer several times before it will show a connection, and then, only for a little while before it drops the connection again. When connected, everything works fine (printing, faxing, scanning).
When the printer is disconnected, the network status has a yield sign with an exclamation point inside. There are no blinking lights on the back where the network cable connects. When it connects (by me plugging and unplugging), the lights start flickering. I've tried several cables including known good ones to rule that possibility out. Cycling the power has no consistent affect. The router is otherwise working fine.
Here are other details that might help:
Model: HP OfficeJet Pro 8600 (N911a)
Firmware: up-to-date
Software drivers: up-to-date
Router: CISCO E3200
Connection: wired network
Static IP address reserved (not connecting with DHCP)
MAC filtering off
Main Computer: Windows 7 Service Pack 1
Wired Connection to the router
Can someone suggest a solution? My best guess is that the network card in the printer is bad, but I am willing to try an easier solution. Thanks.

Hi, are there any other peripherals using the RJ45 ports on the router?
Are you using a static IP address for the 8600?
Please mark the post that solves your issue as "Accept as Solution".
If my answer was helpful click the “Thumbs Up" on the left to say “Thanks”!
I am not a HP employee.

Help with small wired network?

My office has 7 iMacs and 3 MacBooks using ethernet cables to connect via a hub. I'm trying to establish a wired network between these, so as to allow full browsing and read/write access among them while preventing access to any computer not physically connected.
I understand I can set the home folders to shared, but a few problems present:
1. This seems to establish wireless sharing, whereas we need a wired-only network.
2. I understand how to share between accounts on a single computer, say, accounts A and B on computer X. But how to add permissions for accounts on other computers (e.g. account Y on computer Z)?

Yep, I realize that, and it's where I'm stuck at. I'm only seeing two possibilities, neither of which is helpful...
A. allow permissions for "Users & Groups" on the same computer, which ignores the goal of networking users from other computers.
B. allow "Everyone" with a wireless connection, which ignores the goal of creating a network between only the office computers.
So the Receptionist computer wants to allow access to users from the Front Office computer, Technicians computer, and Back Office computer. Back office wants to allow users from the Technicians computer, Front Office computer, and so forth.
But for example, all I can figure out now is how to allow users on the Receptionist computer to allow other users on the Receptionist computer, or else to allow all users from any computer with a wireless connection...

HP CP1525nw - Connect via wired network and wireless ad hoc?

At my job we have our HP 1525nw printer connected into the network printserver via ethernet cable. The printer has its own IP address setup on the network.
With support for XP computers ceasing, a copule of computers will be cut off/blocked from the job's network. One computer is close enough where we can make a USB connection to print. Another is located on another bench. Furthermore, the one that is further away from the printer also can't be upgraded to a compliant Windows OS due to incompatibility with specialized software used to operate equipment hooked up to this computer.
Is it at all possible for this wired network printer to also be setup to print wireless via an ad hoc connection? The idea was perhaps we could install a wireless card on thix XP computer and print wirelessly via a direct connection to the printer, avoiding having to connect to it via the wired network at all. But it is sounding like this wouldn't be possible. Looking for a direct answer before I start shopping around for a wireless PCI card.
This question was solved.
View Solution.

From other posts I have read, I think the CP1525 can be either ethernet or wireless not both at the same time. That will prevent you from setting up with an adhoc network the way you described.
You might try an inexpensive wireless router with a build in print server attached to the usb port. then add wireless USB wireless dongles to the XP computers. Be sure you make sure that the wireless dongles support XP. Also for security purposes you will want to leave the wireless router disconnected from your network.
If your fairly tecky and you don't mind playing a bit you could check your local thrift store for a used router with a print server. For printing you don't need the fastest wireless available. Just make sure it is a b/g router (not a B only one).
Treefrog
Please mark the post that solves your problem as "Accepted Solution"
Sometimes it takes several posts back and forth to get to a solution - please be patient.
I am employed by HP

CONNECT A B210 TO A WIRED NETWORK

Hello.
I want to connect my HP B210 printer to the wired network. I just get a USB to ethernet converter?

This printer does not support wired networks. Sorry.
I was able to find USB to Ethernet adapters for computers, but none for printers. I do not believe this will work for you. If such a device does exist, I cannot guarantee the printer will work consistently as it is not designed to handle network traffic through a USB port.
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Wired network problems

Hi there,
I'm having problems with my wired network and desktop machine running arch.
my problem is the internet connection when browsing keeps appearing to drop when I'm running other internet based things. For instance if I'm downloading a torrent in ktorrent even if the torrent is downloading slowly then browsing becomes impossible. Or if pacman is running browsing again becomes impossible. Sometimes it appears to drop when nothing else is running.
The internet connection is fine because my laptop (also running arch) and on a wired connection works perfectly every time. I have tried swapping from the built-in network card to another one with no success, I have tried changing the cables with no joy.
The internet worked fine on this machine until I reinstalled arch on a different hard disk, i'm completely at a loss as to what the problem could be.

Hi Gcool, here is the output of the 4 commands that you posted
lspci -k
00:00.0 Class 0600: Device 8086:2770 (rev 02)
Subsystem: Device 103c:2a50
00:01.0 Class 0604: Device 8086:2771 (rev 02)
Kernel driver in use: pcieport
00:1b.0 Class 0403: Device 8086:27d8 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: snd_hda_intel
00:1d.0 Class 0c03: Device 8086:27c8 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.1 Class 0c03: Device 8086:27c9 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.2 Class 0c03: Device 8086:27ca (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.3 Class 0c03: Device 8086:27cb (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.7 Class 0c03: Device 8086:27cc (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: ehci_hcd
00:1e.0 Class 0604: Device 8086:244e (rev e1)
00:1f.0 Class 0601: Device 8086:27b0 (rev 01)
Subsystem: Device 103c:2a50
00:1f.1 Class 0101: Device 8086:27df (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: ata_piix
00:1f.2 Class 0104: Device 8086:27c3 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: ahci
00:1f.3 Class 0c05: Device 8086:27da (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: i801_smbus
01:00.0 Class 0300: Device 1002:7181
Subsystem: Device 1462:0400
Kernel driver in use: radeon
01:00.1 Class 0380: Device 1002:71a1
Subsystem: Device 1462:0401
02:01.0 Class 0c00: Device 11c1:5811 (rev 70)
Subsystem: Device 103c:2a50
Kernel driver in use: firewire_ohci
02:03.0 Class 0200: Device 10ec:8139 (rev 10)
Subsystem: Device 10ec:8139
Kernel driver in use: 8139too
02:04.0 Class 0280: Device 1814:0201 (rev 01)
Subsystem: Device 1814:2560
Kernel driver in use: rt2500pci
02:08.0 Class 0200: Device 8086:27dc (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: e100
ip link
00:00.0 Class 0600: Device 8086:2770 (rev 02)
Subsystem: Device 103c:2a50
00:01.0 Class 0604: Device 8086:2771 (rev 02)
Kernel driver in use: pcieport
00:1b.0 Class 0403: Device 8086:27d8 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: snd_hda_intel
00:1d.0 Class 0c03: Device 8086:27c8 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.1 Class 0c03: Device 8086:27c9 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.2 Class 0c03: Device 8086:27ca (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.3 Class 0c03: Device 8086:27cb (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: uhci_hcd
00:1d.7 Class 0c03: Device 8086:27cc (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: ehci_hcd
00:1e.0 Class 0604: Device 8086:244e (rev e1)
00:1f.0 Class 0601: Device 8086:27b0 (rev 01)
Subsystem: Device 103c:2a50
00:1f.1 Class 0101: Device 8086:27df (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: ata_piix
00:1f.2 Class 0104: Device 8086:27c3 (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: ahci
00:1f.3 Class 0c05: Device 8086:27da (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: i801_smbus
01:00.0 Class 0300: Device 1002:7181
Subsystem: Device 1462:0400
Kernel driver in use: radeon
01:00.1 Class 0380: Device 1002:71a1
Subsystem: Device 1462:0401
02:01.0 Class 0c00: Device 11c1:5811 (rev 70)
Subsystem: Device 103c:2a50
Kernel driver in use: firewire_ohci
02:03.0 Class 0200: Device 10ec:8139 (rev 10)
Subsystem: Device 10ec:8139
Kernel driver in use: 8139too
02:04.0 Class 0280: Device 1814:0201 (rev 01)
Subsystem: Device 1814:2560
Kernel driver in use: rt2500pci
02:08.0 Class 0200: Device 8086:27dc (rev 01)
Subsystem: Device 103c:2a50
Kernel driver in use: e100
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1a:92:de:71:43 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.2/24 brd 192.168.0.255 scope global eth0
inet6 fe80::21a:92ff:fede:7143/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:e0:4c:39:00:07 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 00:90:4b:d6:30:8a brd ff:ff:ff:ff:ff:ff
ip route
default via 192.168.0.1 dev eth0
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2
As you can see currently I have the onboard LAN card enabled and connected to the network, the Realtek card isn't connected to the network and nor is the wireless card. I only re-anabled the onboard card to test to make sure that it wasn't a problem with the Realtek card, and it doesn't seem to be.
I have copied all my data across the network onto my server without a problem, therefore it seems to be just a problem accessing the internet. Because all my data is now sat on my server it means I can do a completely fresh install onto this computer but i know that isn't really the Linux way
This machine does dual boot with windows so I might boot into window to see if the problem happens when using that.

2 wired network adapters on 1 computer

Similar Messages

Maybe you are looking for