Andrew Knoke_1 Absent Member.
Absent Member.
2371 views

BadServer Name Cache on Win7 NWClient 2

I have the Windows 7 NwClient SP1 IR1 installed on my workstation. I
have a delay of around 40 seconds when connecting to our Windows
Servers. We had this same issue with our XP machines with the 4.91
client and we were able to fix this by making a change in the Novell
Client Properties | Advanced Settings and setting the Bad Server Name
Cache Enabled = On, Bad Server Name Cache Timeout = 0, and Name
Resolution Timeout=1. Also unselecting DNS in the protocol preference
and finally making a reghack and adding the badserver ip addresses.

These settings are no longer available under the Windows 7 client.
Looking in the forums I can see others have had what seems like the same
issue but from what I can tell nothing has been resolved.

http://forums.novell.com/novell-product-support-forums/open-enterprise-server/oes-platform-independent/oes-client-windows/400412-slow-windows-file-share-access-vista-7-a.html

Is there a fix for this or are we left to just wait when connecting to a
Windows server?
Labels (1)
0 Likes
4 Replies
Highlighted
sselaya
New Member.

Re: BadServer Name Cache on Win7 NWClient 2

We miss that feature as well for other reasons, but the only work around we have found to speed up connections to the Windows servers is to go to Control Panel->Network and Sharing Center->Change Adapter Settings->Advanced Menu->Advanced Settings->Provider Order and then move Microsoft Windows Network to the top.
0 Likes
Andrew Knoke_1 Absent Member.
Absent Member.

Re: BadServer Name Cache on Win7 NWClient 2

Yeah, we already do that too. Helps a little but the BadServer option
was like night and day for us.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: BadServer Name Cache on Win7 NWClient 2

you might try to disable the dns client on the w7 client. although the name
suggests that it is the dns client, it is merely the dns cache.

> Yeah, we already do that too. Helps a little but the BadServer option was
> like night and day for us.


0 Likes
Andrew Knoke_1 Absent Member.
Absent Member.

Re: BadServer Name Cache on Win7 NWClient 2

Yeah, we already do that too. I see their is a new client out (IR3) I
am going to give that a try. I will let you know if it makes any
difference.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.