Latest Novell Client on Windows 7 PCs fixes Office delays

At a client site with Windows 7 (both 32-bit & 64-bit) workstations running older Novell Client 2, Office 2007 & 2010 was experiencing delays in navigating the file/open dialog boxes. Sometimes the presentation of the folders and files would be quick, but frequently there was a 10 to 45 second delay at displaying the folders and their contents. This problem came on suddenly about early March 2015 (about three weeks ago for this post). I believe some Windows Update triggered the problem. It was affecting Windows 7 clients with a mix of Client 2 SP2 and Client 2 SP3.
I installed the Novell Client 2 SP3 for Windows (IR10a) on the affected PCs and the users report the problem has gone away the very next day.
The site is running a Classic Netware server 6.5.8.
Warren Frush
Computer Studios

Great information; thank-you for posting back your results.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Similar Messages

  • Novell Client for Windows 4.91 SP2 supported on Windows 2008

    Hi Friends
    Can Novell Client for Windows 4.91 SP2 Installed on the Windows 2008 Server. if it can be installed is their any know issues.
    Thanks
    Kaniyath

    Originally Posted by AndersG
    Kaniyath,
    > Can Novell Client for Windows 4.91 SP2 Installed on the Windows 2008
    > Server. if it can be installed is their any know issues.
    >
    1. This is the forum for windows 9x
    2. There is no official client for 2008 (yet), but several posters have
    claimed success with the Vista client.
    - Anders Gustafsson (Sysop)
    The Aaland Islands (N60 E20)
    Discover the Novell forums at http://forums.novell.com
    Novell does not monitor these forums officially.
    Enhancement requests for all Novell products may be made at
    Enhancement Request
    Thanks for the Update, Sorry for posting my query in the wrong forum.

  • Group policy template for Novell Client for Windows 7

    Does anyone know if there is a group policy template for the Novell Client for Windows 7? I find it really hard to believe that Novell has not yet released one, but I cannot find one anywhere. We use ZCM 11.2, and I really need to be able to send out settings for the client via a group policy.
    By the way, I am also posting this on the Novell Client forum, but since this is also a ZCM thing, I am hoping I might get some feedback here.
    Rick P

    Two recent/new resources are available for the Novell Client 2 SP3 for Windows:
    Cool Solutions AppNote: Novell Client 2 SP3 for Windows: Registry Settings
    Novell Client 2 SP3 for Windows: Registry Settings | Novell User Communities
    Cool Solutions Tool: Group Policy Administrative Template for Novell Client 2 SP3 for Windows
    Group Policy Administrative Template for Novell Client 2 SP3 for Windows | Novell User Communities

  • Removing Novell Client from Windows 7

    Hello,
    We have an issue with programs running slowly on our SUSE Linux server 11.0. We set up a test machine with Windows 7 without Novell Client and the same programs run extremely fast. (They run fast on a Windows 2008 server too with or without the client.) This is great for the new test machine but I have about 20 workstations that need to have the Client removed. If we remove it through control panel (both NICI and Novell Client - whatever version is installed) the programs are still slow. However, if we do a restore to the time before the Novell client was installed, the machine is fast. Because these machines have had the Novell Client installed for months, we cannot go back to an old restore point. Is there some registry file or other file that needs to be removed or changed to make the computer like it was installed without the Novell Client? I really do not want to have to rebuild 20 computers in order to fix this. I have researched the web and forums and cannot find any information about anything else that needs to be changed when the Novell client is removed. FYI - this is the same on our few Windows XP machines with the appropriate last updated Client on them.
    Any help would be welcome!
    Susan

    We have had many issues with the Novell Client / Windows 7. Here is what we have done to get to an acceptable point.
    We are running OES 11SP1 fully updated up until July (Getting ready to apply more updates), we are also talking about switching from CIFS to Samba as we have been seeing some weirdness with CIFS and NSS disconnects.
    OES11 SP1 - Primary File Server NSS with CIFS
    OES11 SP1 - DSFW/DNS Server for Domain Authentication for the CITRIX Servers, this server also runs ZCM 11.2.2 (Also going to update this as we need windows 8 support and the ZCM Agent has some issues at this level; however ZCM has a horrible way to apply updates and is time consuming)
    OES11 SP1 Squid Proxy With transparent user authentication using LDAP with SquidTrust. Also has NSS Shares
    Other servers exist as well.
    We standardized on Novell Client 2 SP3 or Greater. Currently SP3 IR3 is what is in use. But prior to SP3 the client had many issues for us.
    Also, We do not use Group policy with ZCM (We tried But it was painful and slow and policies would randomly just quit working / remove themselves) we reverted back to just digging in and finding the registry keys. If a key only existed in the Policy Section we put it there and do a GPUPDATE /force on login.
    Server Settings:
    Disable OPLOCKS
    Workstation Settings:
    NW Client Settings
    File Commit (Enabled)
    File Cache (Disabled) - NW Client Setting
    Name Services DNS / SLP Only (Default on the newer Netware Client)
    Win7 Machine Settings:
    Static DNS Server - Set to the internal servers only. No external server set. The win 7 machines for some reason would use the secondary DNS Server randomly instead of the primary, never really dug in on why but disabling / removing a public DNS Server as the secondary and adding in a second internal.
    MS Client For Microsoft Networks Remove, We tried changing the preferred order on the network adapters with no help. I believe the fact that we are running CIFS on the Server side the client is having issues with deciding on how to connect to the NSS Volumes when the client is installed. With the MS Client removed we see a huge improvement In the Novell client.
    Libraries Disable - Registry - We redirect Documents Folders and such and these libraries are wanting to index the locations. As the Libraries consist of multiple locations.
    Offline Files Disable - Registry
    Windows Search Disable Registry (Service)
    Zone Mapping - Registry Adds the servers & domain to the Trusted list for the OS (Even though it says Internet Explorer its used by other portions of the OS)
    User Access Control Registry
    I have others that helped but this is the short list of changes that made major improvements.
    When I have a moment I will look back and see if there are other major changes. This is just what I remember.

  • Novel Client for Windows 3.1

    I recently was asked to support a windows 3.1 server with a Novel client
    on top of it. It looks like the client has crashed so I am trying to find
    out where I can get a copy of the Novel client that will work with
    windows 3.1.
    Does anyone have any ideas?
    Thanks
    Vic

    [email protected] wrote:
    > I recently was asked to support a windows 3.1 server with a Novel client
    > on top of it. It looks like the client has crashed so I am trying to find
    > out where I can get a copy of the Novel client that will work with
    > windows 3.1.
    NetWare DOS Client
    http://www.novell.com/coolsolutions/tools/13555.html
    Keep scrolling down past the link for dw271e.zip (which is the 32-bit
    client for DOS and Windows 9x), and you'll get to the links for
    vlm121_x.exe, which represent the Novell Client probably last used for
    Windows 3.10.
    Or, KEEP scrolling down and you can scroll right into 1994 and a link
    to where NETX v3.32 PTF may be found.
    Alan Adams
    [email protected]
    (for email, remove the crumbs)

  • WWW Location of the Novell Client for XP supporting IP Gateway Services

    When connecting Windows XP workstations to the SBS 6.0 server through the
    Novell Client 4.9SP1a for Windows XP, there are no services within 4.9
    for IP Gateway included. As many of you know, by using BorderManager as
    the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
    accessing the Internet need the IP Gateway service installed with the
    client. The Novell Client CD-ROM shipped with the Novell SBS 6.0 media
    has clients for Windows NT/2000 (outdated) but none are compatible for
    Windows XP (it appears that Novell had not updated their Novell SBS 6.0
    media since they started shipping it). In addition, the online
    documentation included with the media is outdated (e.g. BorderManager 3.6
    docs for BorderManager 3.7 being shipped) and do not mention anything
    about configuring Windows XP clients for Novell IP Gateway services.
    I have thoroughly looked within Novell's Support site the past few weeks
    for:
    + The original Novell Client 4.9 (prior to support packs) to see if that
    version of the client has IP Gateway services included (file not found or
    listed).
    + Previous Novell Clients for Windows XP to see if those versions support
    IP Gateway services. (Support Pack versions only are listed, but no
    original versions, and do not contain Novell IP Gateway services).
    + Any instructions or tips for configuring the Novell IP Gateway services
    within the Novell Client 4.9 or earlier versions for Windows XP(documents
    are non-existent).
    All of the above leads the following question:
    Can someone please direct me to the location to where the proper
    Novell Client for Windows XP supporting Novell IP Gateway services?
    Since Windows XP has been around for a few years now, one would think
    Novell would have developed a client for it that possesses Novell IP
    Gateway services by now to be used with BorderManager. Correct? If so,
    where is it? In addition, one would think Novell would include the media
    supporting the current software they are shipping, not outdated ones.
    (Or at least, ensure their outsourced sales services are doing so.) In
    addition, one would also think Novell would at least provide the
    necessary tools/files necessary to at least to have the ability to
    install their products out of the box - instead of forcing their
    consumers to purchase unnecessary additional support services for
    something they should have included within their media package or website
    at the start.
    Nevertheless, I appreciate any input where to find the appropriate Novell
    Client for Windows XP supporting Novell IP Gateway services.
    Thanks,
    EricV

    In article <cb60c.5596$[email protected]>, wrote:
    > As many of you know, by using BorderManager as
    > the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
    > accessing the Internet need the IP Gateway service installed with the
    > client.
    >
    This is simply not correct. Novell has not been providing IP gateway
    functionality within Client32 for a long time, because it is not needed,
    and it had serious limitations.
    I haven't had a client using IP Gateway for many years now, and I have a
    *lot* of BorderManager clients.
    The alternative to IP Gateways is a combination of proxies and NAT w/filter
    exceptions.
    Craig Johnson
    Novell Support Connection SysOp
    *** For a current patch list, tips, handy files and books on
    BorderManager, go to http://www.craigjconsulting.com ***

  • Novell Client with NCS cluster behind firewall (IP filter)

    I try to connect with Novell Client on Windows to a OES NCS cluster
    behind a firewall. Currently open ports are 524/tcp, 524/tcp, and
    427/tcp for the Master IP Address and the virtual servers.
    This does not work. My first analysis shows that the client tries to
    connect to the host running the Master IP Address with it's primary IP.
    Is this correct? Is there a way to use the Novell Client without
    allowing packets with the destination IP address of the NCS cluster hosts?
    Gnther

    Massimo Rosen wrote:
    > On 29.03.2011 17:22, Gnther Schwarz wrote:
    >> I try to connect with Novell Client on Windows to a OES NCS cluster
    >> behind a firewall. Currently open ports are 524/tcp, 524/tcp, and
    >> 427/tcp for the Master IP Address and the virtual servers.
    >> This does not work.
    >
    > Correct.
    >
    >> My first analysis shows that the client tries to
    >> connect to the host running the Master IP Address with it's primary IP.
    >> Is this correct?
    >
    > Yes, assuming it holds a replica of eDirectory.
    >
    >> Is there a way to use the Novell Client without
    >> allowing packets with the destination IP address of the NCS cluster
    >> hosts?
    >
    > No, because the physical hosts are the ones running and advertising
    > eDirectory, and a client needs to login to edirectory too, in addition
    > to the actual server holding a resource it needs. In essence, you cannot
    > / should not hinder connectivity to any physical server holding
    > writeable eDirectory replicas, and you can not do this for any master
    > replica. At the very least you'll be causeing massive slowdowns, if
    > necessary master replicas can't be reached, it'll be stopped from
    > working entirely.
    Thank you very much indeed for the thorough answer and explanation. We
    adjusted the rules on the router appliance and are able to connect now.
    Ports 524 und 427 are exposed for tcp and udp on all physical and
    virtual servers including the Master IP Address.
    Gnther

  • Network Adminssion Control, 802.1x & Novell Clients to have a single login.

    Hi Sir,
    My customer would like to have OTP, if NAC and 802.1x come into picture. At the moment, they are running Novell client for Windows version 4.9SP2 authenticating to Novell LDAP server.
    How can NAC and 802.1x be integrated into one time password (OTP)? If not what is the alternative best solution can we propose to them ?

    With NAC Phase 1, which uses IOS Routers as the NAD, the Trust Verification occurs using EAP over UDP. User credentials are not part of the items passed by the CTA to the policy server. So however you log into the machine will be your authentication experience.
    With NAC Phase 2, which uses L2 switches as the NAD, the Trust Verification is planned to use EAP over 802.1x. The user will be authenticated and authorized by the switch by way of the ACS AAA server. The 802.1x supplicant that you use will dictate whether or not a single login occurs. Choices for supplicants include the embedded supplicant Microsoft offers and supplicants from 3rd parties, such as Funk.
    So you do not have to wait for NAC Phase 2 to take advantage of NAC today. While planning for NAC Phase 2, it would be a good idea to plan out your 802.1x strategy & even implement 802.1x to make sure it is ready to layer the NAC Trust Verification on top of it.
    Please let us know if you have any follow-up questions.
    thanks
    peter
    ps - pls rate these posts so we know if we have provided you with an answer that helps!

  • Aix db client for windows

    did client access software for windows ships with oracle 8i/9i for aix

    jcasino,
    2003 workstation? XP is the current Windows workstation and Vista is
    the next.
    Though its does state "The Novell Client for Windows 2000/XP/2003
    software allows users of Windows 2000/XP/2003 workstations to access and
    use all of the services available on servers running eDirectory�" in the
    Product Description on the download site rest assured that they meant
    Windows versions 2000/XP/2003 and its supported on Windows Server 2003.
    Tony Pedretti

  • Experience about life without Novell Client?

    Hi,
    got anyone a wider experience about OES Infrastructure without Novell
    Client and W7 Workstations?
    We didn't need absolut highest performance but an absolut stable and
    reliable Environment (24h Healthcare).
    - Is Performance with CIFS Access to OES NSS Cluster Ressources comparable?
    - Is availability comparable (in special Cluster migrations, Filelocking
    on Files)
    Today we run ~250 XP Workstations on OES2
    Cluster/Filesharing/iprint/Zen7 and Groupwise.
    Now we are going to ZCM11 and W7/64bit and think about avoid to use the
    Novell Client for Windows to reduce complexity and switch on Client Side
    to AD-Domain and use OES Infrastructur only for the "Backend".
    Most Novell Services (Groupwise/iPrint) are going to auth to AD too, so
    why should we use Novell Client and the NCP Protocol anymore?
    Is the NCP Protocoll so much better against CIFS in current OES
    Implementations (i'm no Expert in this Things).
    Regards
    Thomas

    On 25.04.2012 06:16, kvishwanath wrote:
    >
    > Welcome to Novell CIFS !!
    >
    > To begin with - "OES Infrastructure without Novell Client on Win 7 is
    > possible by Novell CIFS"
    >
    > To answer your specific questions,
    > - Yes, CIFS has Comparable performance improvement w.r.t. Novell Client
    > in recently released versions like OES2SP3,OES11FP0& Upcoming OES11
    > SP1.
    > - CIFS service is a cluster enabled, It works seamlessly on cluster
    > migration, supports cross protocol lock feature across protocols (CIFS,
    > NCP, AFP).
    >
    >
    > In addition, CIFS supports Distributed File Services(DFS), Dynamic
    > Storage Technology (DST), backup an many more features. Please refer
    > Novell Documentation for more details.
    I know this, but in real life there are always pitfalls...
    >
    > Specific to your infrastructure question of ~250 XP workstations, we
    > have scaled CIFS service up to 4000 connections on single server 3 node
    > cluster setup. Howe ever we are interested to know more details on your
    > setup and infrastructure details further on this.
    >
    What would you like to know?
    Most infos are on my first post.
    We get more and more Windows Applikations who need a Windows Server as
    Plattform for Services, Shares and Authentication.
    In the past we create lokal "system" Accounts on these Applikation
    Servers and map there Shares with help of the Loginskripts.
    like map use R: \\app-server\files password /user:<systemaccount>
    But now we are low on Drive Letters...
    So now we think about to bring the Applikation Server and Windows
    Workstation into AD-Domain for using same User Accounts/Passworddatabase
    and use the UNC Syntax for this kind of Applikations.
    Or we use some Applikations/Infrastruktur who use "transparent" Login
    with AD Authentication (sp. Citrix) or use this as Authentication Point.
    And that's our thoughts about CIFS and Novell Infrastractur in General.
    Regards
    Thomas

  • I need drive for Novell Client 4.91.3.2006119for netware 6.5

    I need window 8 drive for novell client 4.9 sp3

    Mostlysunny wrote:
    > I need window 8 drive for novell client 4.9 sp3
    This is the forum for NetWare development support and I suspect you're not
    asking about NetWare development but instead asking for a Novell Client
    that can be installed on Windows 8. If so, I suggest you repost in the
    Novell Client for Windows support forum @
    http://forums.novell.com/novell-prod...lient-windows/
    HTH.
    Simon
    Novell/SUSE/NetIQ Knowledge Partner

  • Novell Client on SuSeDesktop 12.3

    Hi everyone,
    is it possible to install the latest Novell Client on the latest openSuSE 12.3? I can't find Novell Client solutions for Versions later than openSuSE 11 :( When i'm installing the Client via this instruction:
    https://www.suse.com/communities/con...-opensuse-112/
    I'm not able to open Novell Connections, Login or Tray. When I want to start this programs, nothing happens. I'm new in the linux world so forgive me pls :D

    I just tried this to see what happens, and I rapidly get into a dependency snarl during the installation. So I'm not sure how you got it to install cleanly, i.e. without cheating. There may be a means to get around this. But to be honest unless you NEED ( rather than WANT ) NCL to accomplish something in particular it may be easier going with FTP / CIFS / DAV / Filr / ... to get to your files.
    If you are going to get it to work you would need to build the NCL kernel modules, the ones included would not not work and might result in the services failing to start and the other symptoms you have. And make sure that any dependancy issues zypper comes up with are fully resolved. THEN you get into the missing .so shenanigans that is referenced in the thread you cited. And even then you are using NCL on an unsupported platform, as none of the OpenSUSE versions were supported, only the SLE versions.
    So you may be a couple symbolic links away from success, or miles away through the briar.
    -- Bob

  • Novell Client and Login Scripts?

    All:
    I'm a former administrator of NetWare 3.x, 4.x and 5.x systems and am
    intrigued by the NLSBS 9 offering. I have downloaded the trial version
    and have installed it on a test server.
    Since I am "old school", I was wondering if I could use the Novell Client
    for Windows XP and login scripts to automatically map shares using groups
    like I did back in the day.
    I'm very new to the Novell/Linux world since every organization I've
    worked for in the past 10 years abandoned NetWare for Windows. I'm sure
    a LOT has changed since the Linux OS was brought on board, so I thought
    I'd ask.
    Thanks,
    Greg

    Not sure. It would depend on whether Novell is still offering a product upgrade to the OWS from Windows 2000 SBS and what that price looks like. Otherwise, I was more thinking about the software side itself, re: the Linux side. Either way will work. Just work out the figures.
    >>> <[email protected]> 5/23/2006 5:02 am >>>
    I guess I'm looking at it this way: If I purchase the 5-user upgrade
    license of NLSBS for $211.00 which includes upgrade protection, then
    according to Novell, I can upgrade to OWS for free after July 31st. A 1-
    user license for OWS at CDW is about $125.00. $125.00 x 5 = $625.00.
    Is my logic flawed?
    > Why not just get the Open workgroup suite? Its basically the same
    thing, =
    > but you will have todays licences instead of the licence that is
    already =
    > obsolete according to Novell.
    >
    > >>> <[email protected]> 5/17/2006 12:30:13 pm >>>
    > Will do. Thanks guys!
    >
    > I'm getting ready to pull the trigger on purchasing the Novell Linux=20
    > Small Business Suite product. I'm going to get the Upgrade version =
    > with=20
    > 5 users licenses and one year of upgrade protection for a little over=20
    > $200.00 from CDW. I guess I can get by with the Upgrade version since =
    > I=20
    > have a full retail copy of Microsoft SBS 2000 still in the
    shrinkwrapped=20=
    >
    > box. Also, a representative of Novell told me in an e-mail today that =
    > if=20
    > I have upgrade protection on NLSBS, then I can upgrade to the new =
    > Novell=20
    > Open Workgroup Suite for free when NLSBS goes out at the end of July.
    >
    > Sounds like a win-win to me...
    >
    > Thanks again,
    > Greg
    >
    > > I also had a link to a cool solution, that explained how to use
    LDAP=20
    > etc.. =3D
    > > to link up NDS to the Linux box so you could use that to manage user
    =3D
    > > accounts.
    > >=20
    > > Let me know if you need that and I can dig it up.
    > >=20
    > > >>> <[email protected]> 5/16/2006 10:05:48 am >>>
    > > All:
    > >=20
    > > I'm a former administrator of NetWare 3.x, 4.x and 5.x systems and =
    > am=3D20
    > > intrigued by the NLSBS 9 offering. I have downloaded the trial=20
    > version=3D20
    > > and have installed it on a test server.
    > >=20
    > > Since I am "old school", I was wondering if I could use the Novell =3D
    > > Client=3D20
    > > for Windows XP and login scripts to automatically map shares using =3D
    > > groups=3D20
    > > like I did back in the day.
    > >=20
    > > I'm very new to the Novell/Linux world since every organization =
    > I've=3D20
    > > worked for in the past 10 years abandoned NetWare for Windows. I'm
    =3D
    > > sure=3D20
    > > a LOT has changed since the Linux OS was brought on board, so I=20
    > thought=3D20
    > > I'd ask.
    > >=20
    > > Thanks,
    > > Greg
    > >
    >

  • Novell Client for Ubuntu & Rhel

    Hi All
    I need suggestion & help on the below requirement
    Requirement: I am planning to install edirectory directory service for my customer, since the requirement is to have a Directory Service like AD, & to provide logging service to the directory, & to have all the user data & home directories on the server. The users have different desktops like Windows XP,7,RHEL & Ubuntu desktops. I need Novell Client to install on all the user machines & provide logging services.
    1) Is edir can be used to apply policies & group policies like AD.
    2) Novell Client for RHEL & Ubuntu
    3) To create volumes on the OES (like we do on netware servers) to share the volumes to the users.
    4) iManager is installed but the browser is unable to open the page.(object not found)
    5) Users Home Directories should be stored in server.
    Server OS: SLES 10 SP4 32-bit
    Applications: OES2 SP3 32-bit

    baranii wrote:
    > 1) Is edir can be used to apply policies & group policies like AD.
    By itself, no. You would either need to use OES2 which includes Domain
    Services for Windows, which is essentially AD emulation on top of eDir,
    or you would need to use ZENworks which provides extensive policies and
    desktop management capabilities. ZENworks will work with either eDir
    or AD.
    > 2) Novell Client for RHEL & Ubuntu
    This does not exist. There is only a Novell Client for Windows and for
    SUSE Linux.
    > 3) To create volumes on the OES (like we do on netware servers) to
    > share the volumes to the users.
    That's easily done with OES2. You can create NSS volumes just like on
    NetWare, or even share Linux directories as NCP volumes accessible from
    any Novell client.
    > 4) iManager is installed but the browser is unable to open the
    > page.(object not found)
    That's going to be its own issue and should go into either an OES2 or
    iManager forum.
    > 5) Users Home Directories should be stored in server.
    Not a problem, at least with storing home directories on NSS. I'm not
    sure about storing them in a non-NSS filesystem.
    > Server OS: SLES 10 SP4 32-bit
    > Applications: OES2 SP3 32-bit
    OES2 SP3 should meet many of your needs it appears. You can get
    policies with DSfW, but you have to install DSfW at the same time you
    install the server. You can't (currently) add it after the fact.
    Novell Knowledge Partner
    Enhancement Requests: http://www.novell.com/rms

  • About novell client install

    Hi All
    my customer have some branch office in Eu & US, there are some OES File Server, he want to perform data migration to windows server (OES and Windows File Server on the same branch office), but Default NSM Engine Server on Aisa. I want to ask if I install Novell client on windows File Server...the migration-Data traffic only keep on branch office local LAN or still return to Engine Server through WAN(VPN) ?
    thanks!!
    wyld

    On 12/4/2013 2:16 AM, wyldkao wrote:
    >
    > HI
    > I re-read admin guide...the novell client indeed install on Engine
    > Server, but I find it said
    > ==>"If Agents are deployed as a part of a Novell Storage Manager
    > installation, these agents are individually used for migration if the
    > Novell Client is installed on them. In order for an agent to participate
    > in a migration, the server that has the agent installed must also have
    > the Novell Client installed."
    >
    > If my Engine / Agnet locate in different location (leased line), I
    > should install Novell client on Windows File Server let it receive
    > command from Engine and direct copy data from OES Server , right ?
    >
    > wyld
    >
    >
    Yes, it would be best to install the Novell Client and an Agent on that
    server.
    -- NFMS Support Team

Maybe you are looking for