Re: Pathworks install/config problem

From: PEN (paul.nuneznosp_at_mhp.com)
Date: 01/28/05 

Date: Fri, 28 Jan 2005 11:12:16 -0500

Hi,

Regarding ODS5 support, you may be correct - v6.0B may not support
_creating_
the SAM files on an ODS5 volume (but you're past that now).

The gethostbyname error indicates the server didn't get a response returning
the IP address of the local system. Are you otherwise able to translate the
local hostname to an IP address (i.e., using some TCPWare command equivalent
to $ UCX SHOW HOST <fully-qualified-domain-name>)?

The sequence, when running TCP/IP Services for OpenVMS, goes like so:

   The Advanced Server issues a gethostname call.

   TCP/IP Services returns the fully qualified domain name derived from the
logicals TCPIP$INET_HOST and TCPIP$INET_DOMAIN.

   Advanced Server issues a gethostbyname call.using the name returned
above as an argument.

  TCP/IP Services will either return information from the local host
database (most likely) or query a DNS server to get the address and return
it to Advanced Server.

Paul

"issinoho" <issinoho@gmail.com> wrote in message
news:10vk5bhmd64ioac@corp.supernews.com...
> Paul, thanks for that.
>
> This is the newest version of Pathworks I have access to so for the moment
> my only option is to persevere.
>
> The debug logical you supplied had no effect so I spent last night pulling
> apart command files until things boiled down to PWRK$SAMCHECK.EXE failing
> when it tries to build the SAM datafiles. My theory at this point was that
> the older software was crashing out because I am using an ODS-5 disk (for
> whatever reason).
>
> I have a second server (VAX) running the same version of PW successfully
> so I copied the SAM datafiles across, edited the LANMAN.INI accordingly
> and re-ran PWRK$CONFIG. Lo-and-behold the procedure ran through and worked
> perfectly.
>
> So starting up PW gets about half of the processes running. PWRK$KNBDAEMON
> fails as follows,
>
> Fri Jan 28 10:19:34 2005 get_ip_addr: gethostbyname error: 0
>
> This is definitely a TCPWare issue as switching to UCX resolves the
> problem (although for various other reasons I don't want to use UCX)
>
> I think I am banging my head off a wall here, some combination of ODS-5,
> Pathworks & TCPWare is combining to cause me grief. Being only a hobbyist
> I don't have resources to get newer versions of Pathworks, I don't suppose
> anyone can oblige?

Relevant Pages

  • RE: fallback solution for NT 4.0 upgrade
    ... Regarding the backup of SAM database, I would like to suggest some ... Using REGBACK will copy the records from the SAM into a new file. ... BACKUP directory already exists on drive C, and Windows NT is also ... | I have an NT 4.0 server I'd like to upgrade to 2000. ...
    (microsoft.public.windows.server.migration)
  • Re: Cannot Use System Infomation Function
    ... Most welcome, Sam. ... Scroll down to Server and make sure it is started. ... Troubleshooting Windows XP ... > I should mention also that when I close the System Information program, ...
    (microsoft.public.windowsxp.general)
  • Re: Cannot Use System Infomation Function
    ... Thanks, Sam. ... > "Can't collect information Access denied to Windows Management ... > Instumentation server on this computer. ... >> My profile has administrator privileges. ...
    (microsoft.public.windowsxp.general)
  • Re: passing object ByRef not updating object references
    ... Thanks for a quick reply Sam, but I'm afraid nothing has changed as of yet. ... Public Sub ClientChangedImplements ... Now I'll keep the client connected and stop the server and in the process, ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Restoring Trusts between client workstations and Domain Contro
    ... copying and pasting a backup of their "Windows Special Folder"? ... >> the server without the benefit of recent backup of SAM and SID's. ... >> go about restoring communication between the client workstations (they ...
    (microsoft.public.windows.server.general)