Dear Leslie,
as far as I know the NT ping works for the 'netbios name' and not for the
'IP hostname'. But unfortunately you can set a different 'IP hostname' and
'netbios hostname' in the NT network properties although MS does not
recommend it.
Please check also the IP configuration with ipconfig /all to see the whole
configuration and if all the services have been started or configured in the
network properties and try to put the hostnames in the lmhost file which
resolves IP to 'netbios hostnames' like in the lmhosts.sam sample file.
Hope that helps,
Christoph Kral
OMV Aktiengesellschaft
F-RZ / Computer Control Center
Lassallestraße 3, A-1020 Wien
Telefon+43-1-40440/2331
Telefax +43-1-40440/62331
Christoph.Kral@omv.com
http://www.omv.co.at
'Nur tote Fische schwimmen mit dem Strom' , M. Gandhi
-----Ursprüngliche Nachricht-----
Von: lclark@us.ibm.com [mailto:lclark@us.ibm.com]
Gesendet am: Donnerstag, 05. Oktober 2000 05:13
An: NV-L@tkg.com
Betreff: [NV-L] Name resolution for Netview for NT
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
|