Anonymous_User Absent Member.
Absent Member.
1398 views

MAS200 slow with Novell client?

We are seeing issue with printing from XP PC's running any verison of
4.9X clients. When going to print the job takes 15-30 seconds to print.
this is not good since were printing customers invoices. Removing the
client and logging to AD/Win2003 resolves the issue?

Any tunning apprecaited!
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: MAS200 slow with Novell client?

pro,

Lets gather some more details on your environment...

Any additional components of the client installed?
What protocols are bound to the client?

What version and SP of Windows?
Windows Event logs showing anything unusual?
Was Windows installed from scratch, a custom image, or an OEM image?

Security or any other driver-based software like firewall, VPN, remote
management or antivirus installed and running?

Then verify that nothing is affecting DNS or any other Windows component in
your AD/Domain environment...

Diagnosing Logon Delays
http://www.windowsitpro.com/Articles/Index.cfm?ArticleID=38325

Take a look at this list and let us know which, if any, of these steps help
with your delays...

Enhance Client32 Performance
http://www.ithowto.com/novell/clientspeed.htm

You might consider getting a network trace looking for any unusual
traffic...

Guidelines to Take a Packet Trace
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10011012.htm

How to use Ethereal to capture a packet trace.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10070788.htm

There is also a registry value to allow you to populate the Bad Address
Cache to prevent the Novell Client from connecting to specific IP
addresses...

How to prevent a client from ever using a server returned in a referral list
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086959.htm

--
Tony Pedretti


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: MAS200 slow with Novell client?

Answers after your questions. they have moved the retail PC's to
AD/Windows 2003 login only and mapping drives to NW home dirs.
> pro,
>
> Lets gather some more details on your environment...
>
> Any additional components of the client installed? iPrint
> What protocols are bound to the client? -IP only
>
> What version and SP of Windows? -SP2
> Windows Event logs showing anything unusual?
> Was Windows installed from scratch, a custom image, or an OEM image? -

Imaged with ZEN when new and apps installed.
>
> Security or any other driver-based software like firewall, VPN, remote
> management or antivirus installed and running? -Symantec AV
>
> Then verify that nothing is affecting DNS or any other Windows

component in
> your AD/Domain environment...
>
> Diagnosing Logon Delays
> http://www.windowsitpro.com/Articles/Index.cfm?ArticleID=38325
>
> Take a look at this list and let us know which, if any, of these steps

help
> with your delays...
>
> Enhance Client32 Performance
> http://www.ithowto.com/novell/clientspeed.htm
>
> You might consider getting a network trace looking for any unusual
> traffic...
>
> Guidelines to Take a Packet Trace
> http://support.novell.com/cgi-bin/search/searchtid.cgi?/10011012.htm
>
> How to use Ethereal to capture a packet trace.
> http://support.novell.com/cgi-bin/search/searchtid.cgi?/10070788.htm
>
> There is also a registry value to allow you to populate the Bad Address
> Cache to prevent the Novell Client from connecting to specific IP
> addresses...
>
> How to prevent a client from ever using a server returned in a referral

list
> http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086959.htm
>
> --
> Tony Pedretti
>
>


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.