A
Aryn-Leah Adelman
In the past couple weeks we have had several clients lose the ability to
browse the network with the Client for Microsoft Networks after automatic
updates have been applied.
They maintain network connectivity but cannot browse using Network
Neighborhood, cannot search for computers on the network and they do not get
their login script drive mappings. The only way they can access a network
share is by typing in the UNC.
Reinstalling the Client for Microsoft Networks seems to resolve the issue
but I would like to know what is causing it and am not comfortable with
randomly reinstalling the client on a bunch of our client workstations.
Has anyone seen this occurring recently or know of a possible hotfix out
there?
If I have posted to the wrong folder please let me know. I tried to find a
WindowsXP.Update newsgroup to no avail.
browse the network with the Client for Microsoft Networks after automatic
updates have been applied.
They maintain network connectivity but cannot browse using Network
Neighborhood, cannot search for computers on the network and they do not get
their login script drive mappings. The only way they can access a network
share is by typing in the UNC.
Reinstalling the Client for Microsoft Networks seems to resolve the issue
but I would like to know what is causing it and am not comfortable with
randomly reinstalling the client on a bunch of our client workstations.
Has anyone seen this occurring recently or know of a possible hotfix out
there?
If I have posted to the wrong folder please let me know. I tried to find a
WindowsXP.Update newsgroup to no avail.