Leslie
I would be inclined to look at Control Panel -> TCP/IP -> DNS and make sure
that the NT machine's hostname and domain name are set correctly. Then I would
run IPCONFIG /ALL and check everything. Then I would put the FQDN and the
hostname in the hosts file, cross-checking against the IPCONFIG /ALL output.
Presumably pinging 127.0.0.1 and pinging the IP address work?
--
Martin Walder
Tivoli Certified Enterprise Consultant
IT Masters (UK) Ltd
Unit 5, CNC House,
Grand Union Office Park,
Packet Boat Lane,
Uxbridge UB8 2GH
Tel: +44 (0) 1895 909 500
Mobile: +44 (0) 771 315 8548
Fax: +44 (0) 1895 909 501
Internet http://www.itmasters.com
lclark@us.ibm.com wrote:
> I found a customer where there is no name resolution whatever for their
> NT servers, it seems they do everything by IP address and Novell clients.
> So the prospective server, which is running as a production fileserver,
> cannot even resolve its own name. A vendor set these up for them.
>
> I expected that if I put its name in winnt\system32\drivers\etc\hosts, that
> it would be able to resolve its own name, at any rate. Hostname returns
> the computer name, and that is in the hosts file, but I cannot ping that
> name. And ovspmd won't start, apparently on account of that.
>
> Any NT experts with ideas? (I'm not one either!)
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> Detroit
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
|