Messed up CDE with Set_Parms

[Greg Fraser_1]

Noticed this post after I ran set_parms from CDE. Now CDE doesn't work. Any Suggestions on how to fix this ?

"just be careful with the "set_parms" to change your ip address - do NOT do this from X-Windows (=CDE), as that stops working then :-(
Log in in text-mode (Graphics Login dialog->Options->command line), THEN call "set_parms ip". "

Thanks

GP
Wodisch

[Sridhar Bhaskarla]

Hi Wodish,

Try login from the command line (or fail-safe session) and see if the hostname is correctly getting resolved to the IP of the system.

#nslookup `hostname`

If not, then you need to fix /etc/hosts to point the hostname to the IP address configured on the system. If you are using DNS, make sure DNS is updated with current IP address for the hostname.

If it works, then make sure you can be able to ping to the localhost.

ping localhost and you should get response back

There is a tool /usr/contrib/bin/X11/dr_dt

Run this tool and it will report the health of your CDE. Fix all the issues it reports.

-Sri

[T G Manikandan]

The problem should be name resolution.

The system is unable resolve its hostname.

Can you just check whether it resolves using

#nslookup hostname
#nslookup ip

Make sure that after changing the ip-address or hostname the change is reflected in the local hosts file.
If you are using DNS then you should check whether the change is reflected in the name server.

As suggested sun dr_dt to check out the warnings and error messages.

Revert

[Angus Crome]

If using DNS as your first lookup, make sure that the host resolves both forward and reverse (FQDN and IP). I have that problem with DNS on Wintel all the time. They do updates and forget to change the reverse lookup table. Messes up all kinds of CDE around here.

[Ravi_8]

Hi, wodisch.

propably you wouldn't have set the hostname.
set_parms works well with CDE. i had similar problem in Tru64 machine wherein hostname was not being set.