0

The main problem is why only 2 PCs can't access the network, yet others can.

  • COM16 can freely access any pc.

  • COM16 is sharing drive D, drive F, and 1 folder.

  • COM11 able to access COM16 only folders, not the drives.

  • COM17 and ADMIN-PC totally not able to access com16

  • IP access also failed.

  • All PCs belong to the workgroup WORKGROUP. No known IP conflicts exist.

All settings shown are from COM17 and are exactly the same as COM16

Network:

Network Settings

Permissions:

Permissions

Ping:

Ping

Sharing Settings:

Sharing settings

LAN Network Settings:

LAN Network Settings

Security Settings:

Security Settings

Disk Sharing Settings:

Disk Sharing Settings

Using Ip in Explorer:

Using Ip in Explorer

  • Use the IPs instead of names. – Overmind Feb 13 '18 at 9:01
  • still the same problem – kai Feb 21 '18 at 5:23
  • That means some configuration is preventing access. It could be a security setting of the anti-virus that overwrites firewall policies, for example. – Overmind Feb 21 '18 at 7:24
  • full removal internet security, restore windows firewall default not even help. – kai Feb 22 '18 at 8:11
  • How are your IPs controlled ? Do you have a firewall/router in the network ? – Overmind Feb 22 '18 at 8:53
0

Assuming the correct services are working, in situations like this one it means some configuration is preventing access. That could be:

  • network firewall with specific rules configured

  • anti-virus

  • anti-virus controlling security settings/firewall

  • the actual windows firewall

  • GPO or general security settings

For each situation, the proper things must be checked: the firewall rules (both for network and for windows), the anti-virus security settings. For AV and firewall the settings can be reset from their configuration and the general security settings can be reset using the secedit command.

Also, note that simply selecting 'public' instead of 'work' or 'home' when connecting a computer to the network will prevent it from being correctly accessible, in which case this can be chanced in several manners, including using powershell's Set-NetConnectionProfile command and -NetworkCategory parameter. This could fix the problem without the need of a full security settings reset.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.