X11 can not connect to display

[jp]

With the 715 at home, connected to a vga monitor, compaq mouse, booted it, X came up fine. Did some stuff, shut it down, took cpu to work, plugged in a different monitor, mouse, keyboard, X tells me 'X server can not connect to :0 ' ... what is going on here? I changed the ip address at work, nothing else, not even host name. Changed ip back to previous value, no change. What is broken, and how? Surely its not the different mouse or keyboard doing this? What is a correct TERM value for a vga monitor - anything special?
tia
jp

[John Meissner]

is the new monitor a different type? if so the sync and refresh rates might be different on the new monitor and out of scan range of what you set them to with the monitor at home

[Ollie R]

Hi JP,

How did you change the IP address?

Ideally you should use "set_parms ip_address".

Ollie.

[K.Vijayaragavan.]

do "set_parms initial" and see that ip address change is happeing effectively.

do nslookup to your hostname. If required check /etc/nsswitch.conf.

Use dr_dt command to find the cause of the problem.

[Steven E. Protter]

If the monitor isn't comatible with the sytsem graphics card you would see nothing.

If you have an error message to read thats not it.

Its the DISPLAY variable.

If you change the workstation IP but don't make sure the .profile, /etc/profile has the IP addy correct in the DISPLAY variable, you will get this problem.

in .profile put this.

DISPLAY=:0.0
export DISPLAY

This should be a solution.

I personally stopped using hostname in the DISPLAY variable because of issues like this.

SEP

[jp]

Well, I changed the mouse to the first one used, and up it came. Hard to believe it is that sensitive to hardware like that....
anyway, it goes again. Didnt notice any messages related to it, so in future.. ???

jp

[Ollie R]

JP,
How about assigning some points too?
You've asked 13 questions so far and not given any points out.........?

[jp]

Ok, now it works...until the next change. Put in a real gateway address, and then it looped trying to start X again - took ages to start swagentd, then snmp startup took forever, and X wont run again (ie no CDE startup). I got in via telnet and gave it a crap gateway addr, and CDE is up again - using set_parms properly. The gateway was added with SAM, so that should have been ok. Is there somewhere else I have to change the startup scripts - it must be looking for a server somewhere (NFS is turned off I think) for SD-UX or X itself .
Any ideas where to go next please.
Every response has points now Ollie, OK?

TIA,
jp