cannot connect to Windows xp

Main Page Forums cannot connect to Windows xp

Tagged: ,

This topic contains 5 replies, has 4 voices, and was last updated by  Anonymous 12 years, 7 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1476

    Anonymous

    I have over 30 machines that I am scanning, one of them I cannot connect to no matter what I do. I have tried all the various troubleshooting steps and enabled all the services suggested in the FAQ. I know that the user and password is correct (I have tried different users as well as there are multiple accounts on the pc – they are admin accounts). 20 of the 30 machines are xp machines similarly configured and they all scan fine. One will not, although It correctly identifies the name of the machine during the scan but hangs on ‘connecting to CIM namespace’ and then comes back with ‘Node couldn’t be scanned with any known method. Check your access password.’ My password IS correct, I’ve tried at least 50 times now. Any suggestions

    #1575

    admin
    Keymaster

    You should really have a look into sharing model in local security policies of those Windows XP computers that cannot be scanned. In my experience, that’s the most common reason: https://www.network-inventory-advisor.com/help.html#faqa1 (solution #4)

    • This reply was modified 10 years, 4 months ago by  admin.
    • This reply was modified 5 years, 7 months ago by  Alex.
    #1573

    Anonymous

    Thanks, that helped as I discovered there were several machines not scanning and now only two are not scanning. Secpol is set correctly on these last two machines, they are correctly identified when I do the scan but get stuck on connecting to CIM namespace and then finally “node couldn’ be scanned with any known method. Check your password, which I know is correct. I have two admin accounts on these machines and tried them both, Firewall is off. Do I need to have certain ports available? I do have a hardware firewall but I think we have allowed for this software in the Hardware firewall, but just to be sure what ports are needed?

    #1560

    Anonymous

    Hello,

    Please check the solutions available here once again: https://www.network-inventory-advisor.com/help.html#faqa1

    If the problem persists, please, try to disable the firewall temporarily.

    To scan using auto-deploying agent utility, please open the ports: TCP 22, UDP 137, TCP 139.

    To scan via WMI, please open the ports: UDP 137, TCP 22, TCP 139, UDP 138, TCP 135, TCP 1051.

    • This reply was modified 10 years, 4 months ago by  .
    • This reply was modified 5 years, 7 months ago by  Alex.
    #2602

    Anonymous

    I have researched this issue before with no luck…..I have 2 notebooks with Windows 7 on them, one Professional on Ultimate, sometimes they can see our Windows 2003 SBE Server just fine along with other computers on the network…other times they can’t see anything but themselves.,
    The only work around I have found for this is to install Windows XP Mode and use that, technically not a practical solution but something that works for the time being. Right now I can ping and access the files on this notebook just fine from an XP machine but I can not see the XP machine for this notebook.
    All computers are on the same Workgroup (Not a HomeGroup), all can access the internet just fine, printers are directly connected to the network and can print just fine but not access folders on individual computers or Servers. All firewalls are disabled ie Avast and Windows. Still nothing. Even though it doesn’t work right now, tomorrow it might work just fine without changing anything. Other times the Windows 7 machine can see the computers but not access the files. This is such a common issue that if you were to Google it, it would pop up under suggestions??? Can anyone help??????

    #2593

    admin
    Keymaster

    How is this related to Network Inventory Advisor?

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.