I am having the same issue, and have found no resolve on TechNet or anywhere
else. We just switched to Active Directory in May 2008.
The policies we're having a problem with are software installation and a few
others. I realize that slow link will prohibit all of the policies we're
having a problem with from running. However, it seems to be a game of
Russian Roulette. We can have a computer lab of 30-40 brand new computers,
with gigabit NICs, and about 10% will detect a slow link. We re-image, and a
different 3 or 4 have the problem. I imaged a lab 3 times in two days with
no computers duplicating the slow link detection. The NICs go to managed
Alcatel switches purchased in 2007, which travel across fiber back to our
datacenter. These switches are not taxed in any way, and the fiber even less
so. Our network manager has searched the KB article that describes the
packet level and ICMP traffic of slow link detection. We're in complete
compliance with the default values, as far as we know and if we have the
whole story there.
One thing I've found that helps on older systems, only a small percentage of
the time, is to try and upgrade the NIC card drivers and set them to a fixed
100Mb Full Duplex instead of Auto-Negotiate.
All the registry settings and group policies I've found have had zero success.
What's probably the MOST frustrating is that we simply cannot change the
values, or even push the Policies that increase slow link detection timeout.
What has worked every time is to "wait it out." What I mean by this is
actually coming back to the PC in 3-4 hours and finding that slow link is no
longer detected. I understand that this detection recurrs every 90 minutes,
no?
Is there any way to change the cached "slow-link" on values on the local PC?
Is there any way to proactively DISABLE "slow-link" detection completely?
Our WAN site (~90 miles from our main campus) doesn't have any problems with
its 10 computers. None detected slow link. They use the same equipment we
have here! There isn't a remote server with domain replication either...
Post by Darren Mar-Eliaone thing I did not see in the thread is a description of the kind of
computer policy you are trying to deploy? For example, registry and security
policy will apply regardless of whether a slow link is detected or not.
Darren
--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
*******************************
Secure and configure your Windows desktops accurately every time without
having to learn or install new technology.
Find out more about Desktop Policy Manager at
http://www.sdmsoftware.com/desktop_management
*******************************
Post by Burnyes i have set it.
Windows SP3 doesnt solve the Problem, a Repair Installation of Windows doesn
t solve it,
the only thing which works is to do a fresh installation which is not a very
good Solution for 100 Clients!
Post by Anthony [MVP]And do you have the "always wait for the network" policy set?
Anthony,
http://www.airdesk.co.uk
Post by Burni have set it already in registry!
The only thing happened was that gpresult shows the slow link setting
and
in
the userenv.txt there is a entry: isslowlink: slow link transfer rate is 0
always download policy.
but the computer policy is still not applied and gpresult shows
"Connected
over a slow link?: yes"
Post by Anthony [MVP]Burn,
If they are connected over a slow link, then the policy to change slow link
settings will not be applied.
http://technet.microsoft.com/en-us/library/cc759191.aspx
Hope that helps,
Anthony,
http://www.airdesk.co.uk
Post by BurnHello we have about 1000 Windows XP Pcs in our Domain,
about 100 of them are not applying Computer Policies but they are applying
User Policies.
gpresult showes me
"Connected over a slow link?: yes"
i have turned of Group Policy slow link detection in the Policy and
on
the
client
showing from that on a connection speed is set to 0 kbps. but the
"Connected over a slow link?: yes" allready exists after gpresult and
Computerpolicies are not applied.
I have joined one of the PCs to a fresh installed Domain with the same
result altough a fresh installed PC works on both Domains.
please help me with this strange Problem!