[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

432.0. "NT client to Dunix server?" by SWETSC::WESTERBACK (Panta rei) Thu Feb 20 1997 13:00

    Question: Is there any special trick needed to backup an NT system to a
    Dunix nsr server? 
    
    WE backup a couple of Dunix systems (running 4.2) to a Dunix server. No
    problem.
    
    Also some NT boxes to an Intel running Legato's 4.3. Worked OK. Now
    there's a problem with that one, so I'd like to temporarily backup NT
    machines to the Dunix one.
    
    Have added the new server to the Servers file, also all relevant
    systems are in Hosts and .rhosts. Nsr services stopped and restarted. 
    Still when I create a NT client on the Dunix server, I get the message 
    "<new_client> is a PC or its RPC is down" or something like that. Am I
    missing something basic?
    
    Rgds,
    Hans
T.RTitleUserPersonal
Name
DateLines
432.1SWETSC::WESTERBACKPanta reiTue Feb 25 1997 02:195
    Anyone? 
    
    I might add that I can ping the server from the clients and vice versa.
    
    Hans
432.2Portmapper on the client?SWETSC::WESTERBACKPanta reiTue Feb 25 1997 06:179
    OK, I just found out that if I start Networker Portmapper Service on
    the clients, I can connect from the server, and also start backups.
    
    Should the portmapper be running on the clients? If so, why isn't it
    setup after a new nstallation. It's set to disabled in the Control
    panel. Or is it only needed between Dunix and NT system?
    
    Rgds,
    Hans
432.3DECWET::LENOXWhy is DECdirect so out of date?Tue Feb 25 1997 07:404
What version are your clients?  For V4.3 clients the portmapper
is started right away...  If you already had another portmapper
running, it would matter, do you?
432.4DECWET::KOWALSKITime&#039;s not for savingTue Feb 25 1997 07:579
Actually, the portmapper is installed as a disabled
service in 4.3, both Alpha and Intel NT, because it's
unnecessary with the latest-rev servers.  Starting
it will do no harm, however (unless, as Amy notes,
you have another portmapper running).  Do you have
the server name in the client's \win32app\nsr\res\servers
file?

Mark
432.5DECWET::LENOXWhy is DECdirect so out of date?Tue Feb 25 1997 10:084
Hmm, are the clients & servers different?  Server that
I installed yesterday has the portmapper on by default
and I certainly didn't do anything.
432.6DECWET::KOWALSKITime&#039;s not for savingTue Feb 25 1997 10:562
Yes, the client and server differ in this respect.
/m
432.7SWETSC::WESTERBACKPanta reiTue Feb 25 1997 13:537
    Server is Dunix Networker 4.2, clients NT 4.3. The server
    name is indeed in the ..\servers file.
    
    You're saying that with Dunix 4.3 I don't need portmapper
    clients?
    
    Hans
432.8DECWET::KOWALSKITime&#039;s not for savingTue Feb 25 1997 14:347
There is no Dunix 4.3.

Keep the portmapper running on your NT clients
if you like.  It helps shutdown performance for
the remote exec server.

Mark
432.9CRONIC::LEMONSAnd we thank you for your support.Tue Feb 25 1997 20:035
    It's been my experience, with V4.3 clients and V4.latest servers on DU,
    that the portmapper service must be running in order for the server to
    identify the client architecture.
    
    tl
432.10SWETSC::WESTERBACKPanta reiWed Feb 26 1997 06:395
    Sorry, my mistake. Of course I'm running Dunix server 4.2A, and NT 
    clients are 4.3.
    
    
    Hans