When I do my Disaster Recovery of my NW server, I get this message after
doing my "mmrecov". The service won't start, after I replace the "res"
folder, and I don't understand why.
Platform = Win2003
This server is standalone (i.e., it is not physically connected to my LAN
at all, so it has no connectivity to my DNS servers, either). The IP
address is valid one for my LAN (xx.xx.7.20). There are no DNS servers
defined.
The hosts files has
127.0.0.1 FQDN-of-this-server shortname
defined. So if I ping the server by name, I do get a response (from
127.0.0.1, obviously). An nslookup fails, however. Would that cause this
error? The gateway address is the normal gateway for this subnet, although
I get the same problem with no gateway defined at all.
Basically: what would cause this problem? What is NW doing, that it thinks
it can't get the address, and how can I convince it that it can get an
address, and start to work, so I can do this recover??
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|