Applications only push out when computer is connected to miniswitch

[Jprunty]

Hello,

 

I have an issue on my windows network where Applications pushed out through Group policy will only install if I connect the computer to a miniswitch/unmanaged switch.

 

If it is plugged directly into the port it will not work (The policy will apply but the software will not install). If I then plug that port into a mini switch, then plug that into the computer it pulls down fine.

 

It seems to be only with windows 10 machines that I have noticed it on, from what I can see win 7 machines pull down the software properly.

 

Please could someone help me with this as I am unsure why this would happen.

 

Thank you for your help.

[Davit2005]

Interesting

 

One of the main differences between managed and unmanaged (dumb switches) is that the unmanaged (dumb) switches have no vlan capability, smart type switches can have vlans though.

 

https://www.comms-express.com/infozone/faq/what-is-the-difference-between-smart-managed-managed-unmanaged-network-switches/

 

So I would check to see what IP address settings you are getting on a client that is working and one that is not, specifically looking at DNS settings and make sure that the client is connecting/authenticating to the domain etc.

 

When logged into a PC open a run box and %NETLOGON% and see if you can identify a faulty Domain Controller by comparing results between PCs that work and those that do not.

 

The other possibility is a faulty switch I guess, I have noticed these to give DHCP issues in the past. I would also run dcdiag commands on the domain controllers to make sure there are no issues that could be effecting.

Edited January 14, 2021 by Davit2005

[Jprunty]

So after looking at another issue I happened across the reason this is not working.

 

Basically, STP being enabled on the switches is causing the problem. If I disable STP on the switch it works. I don't really want to do this as it leaves the network vulnerable against loopbacks.

 

I have tried MSTP and RSTP which have portfast, but still the same issue.

Any ideas?

Edited January 15, 2021 by Jprunty

[robyholmes]

I know this might sound mad, but try plugging the PC directly in to the switch. Ideally by a new patch lead. This might mean you have to move it, but see if that solves it. That might point to bad cabling leading to bad communication which means the tree-spanning can't confirm the port is not looped quick enough.

[sted]

there is a gpo that makes a pc wait longer for network at startup. i wonder if its just taking longer to negotiate speed/duplex etc than the pc by default waits though i cant remember off hand where it is

[FN-GM]

So after looking at another issue I happened across the reason this is not working.

 

Basically, STP being enabled on the switches is causing the problem. If I disable STP on the switch it works. I don't really want to do this as it leaves the network vulnerable against loopbacks.

 

I have tried MSTP and RSTP which have portfast, but still the same issue.

Any ideas?

 

This is 100% a spanning tree issue.

 

Port fast should fix it but you need to enable it on the switch port.

 

What switches do you have?