Prev: Infiniband install
Next: problem with mirrored root
From: jay on 6 Apr 2010 17:02
solaris 10, x86, u8, recent install
java desktop is running.

that is -- logged in as an ordinary user, that user
can run x clients. however, it won't serve any
other system. even with
xhost +
all other systems can't connect to the display.
i've tried the DISPLAY variable in all
combinations of the hostname:0.0
fqdn:0.0 and every user on every other system fails.
even doing an su to root, and trying xclock fails.

jgs# xclock
Error: Can't open display: jgs:0.0
jgs# setenv DISPLAY jgs.arlut.utexas.edu:0.0
jgs# xclock
Error: Can't open display: jgs.arlut.utexas.edu:0.0

this was working before the reinstall. a few versions
of solaris ago there was a screen where it asked
whether you wanted tight or old-fashioned levels of
security. and there was a way to swap between
those two -- a script in /sbin IIRC. well, i can't
find that script. i don't think i was asked that
question during install. or if i was asked, i
blundered past it.

where do i start checking?

thanks in advance.

j.
From: jay on 6 Apr 2010 17:32
On Apr 6, 4:02 pm, jay <g...(a)arlut.utexas.edu> wrote:
> solaris 10, x86, u8, recent install
> java desktop is running.
>
> that is -- logged in as an ordinary user, that user
> can run x clients.  however, it won't serve any
> other system.  even with
> xhost +
> all other systems can't connect to the display.
> i've tried the DISPLAY variable in all
> combinations of the hostname:0.0
> fqdn:0.0 and every user on every other system fails.
> even doing an su to root, and trying xclock fails.
>
> jgs# xclock
> Error: Can't open display: jgs:0.0
> jgs# setenv DISPLAY jgs.arlut.utexas.edu:0.0
> jgs# xclock
> Error: Can't open display: jgs.arlut.utexas.edu:0.0
>
> this was working before the reinstall.  a few versions
> of solaris ago there was a screen where it asked
> whether you wanted tight or old-fashioned levels of
> security.  and there was a way to swap between
> those two -- a script in /sbin IIRC.  well, i can't
> find that script.  i don't think i was asked that
> question during install.  or if i was asked, i
> blundered past it.
>
> where do i start checking?
>
> thanks in advance.
>
> j.

sorry. meant to include this:
jgs# routeadm -p
ipv4-routing persistent=disabled default=disabled current=disabled
ipv6-routing persistent=disabled default=disabled current=disabled
ipv4-forwarding persistent=enabled default=disabled current=enabled
ipv6-forwarding persistent=disabled default=disabled current=disabled
ipv4-routing-daemon persistent="" default=""
ipv4-routing-daemon-args persistent="" default=""
ipv4-routing-stop-cmd persistent="" default=""
ipv6-routing-daemon persistent="" default=""
ipv6-routing-daemon-args persistent="" default=""
ipv6-routing-stop-cmd persistent="" default=""
routing-svcs persistent="route:default ripng:default"
default="route:default ripng:default"
From: jay on 6 Apr 2010 18:11
On Apr 6, 4:32 pm, jay <bigcra...(a)gmail.com> wrote:
> On Apr 6, 4:02 pm, jay <g...(a)arlut.utexas.edu> wrote:
>
>
>
> > solaris 10, x86, u8, recent install
> > java desktop is running.
>
> > that is -- logged in as an ordinary user, that user
> > can run x clients.  however, it won't serve any
> > other system.  even with
> > xhost +
> > all other systems can't connect to the display.
> > i've tried the DISPLAY variable in all
> > combinations of the hostname:0.0
> > fqdn:0.0 and every user on every other system fails.
> > even doing an su to root, and trying xclock fails.
>
> > jgs# xclock
> > Error: Can't open display: jgs:0.0
> > jgs# setenv DISPLAY jgs.arlut.utexas.edu:0.0
> > jgs# xclock
> > Error: Can't open display: jgs.arlut.utexas.edu:0.0
>
> > this was working before the reinstall.  a few versions
> > of solaris ago there was a screen where it asked
> > whether you wanted tight or old-fashioned levels of
> > security.  and there was a way to swap between
> > those two -- a script in /sbin IIRC.  well, i can't
> > find that script.  i don't think i was asked that
> > question during install.  or if i was asked, i
> > blundered past it.
>
> > where do i start checking?
>
> > thanks in advance.
>
> > j.
>
> sorry.   meant to include this:
> jgs#  routeadm -p
> ipv4-routing persistent=disabled default=disabled current=disabled
> ipv6-routing persistent=disabled default=disabled current=disabled
> ipv4-forwarding persistent=enabled default=disabled current=enabled
> ipv6-forwarding persistent=disabled default=disabled current=disabled
> ipv4-routing-daemon persistent="" default=""
> ipv4-routing-daemon-args persistent="" default=""
> ipv4-routing-stop-cmd persistent="" default=""
> ipv6-routing-daemon persistent="" default=""
> ipv6-routing-daemon-args persistent="" default=""
> ipv6-routing-stop-cmd persistent="" default=""
> routing-svcs persistent="route:default ripng:default"
> default="route:default ripng:default"

okay, looks like i'm close to getting it sorted. i was
looking for the wrong script name. the correct name
is
netservices

and this fixed my problem for the moment:

netservices open

sorry to bother you. i'd been chasing this for
a couple of days with no luck. finally changed
what i was searching in google and found the
hint in some old install instructions.

any opinions on how dangerous it is to run
w/ netservices open vs. netservices limited ?

j.
From: Richard B. Gilbert on 6 Apr 2010 18:42
jay wrote:
> On Apr 6, 4:32 pm, jay <bigcra...(a)gmail.com> wrote:
>> On Apr 6, 4:02 pm, jay <g...(a)arlut.utexas.edu> wrote:
>>
>>
>>
>>> solaris 10, x86, u8, recent install
>>> java desktop is running.
>>> that is -- logged in as an ordinary user, that user
>>> can run x clients. however, it won't serve any
>>> other system. even with
>>> xhost +
>>> all other systems can't connect to the display.
>>> i've tried the DISPLAY variable in all
>>> combinations of the hostname:0.0
>>> fqdn:0.0 and every user on every other system fails.
>>> even doing an su to root, and trying xclock fails.
>>> jgs# xclock
>>> Error: Can't open display: jgs:0.0
>>> jgs# setenv DISPLAY jgs.arlut.utexas.edu:0.0
>>> jgs# xclock
>>> Error: Can't open display: jgs.arlut.utexas.edu:0.0
>>> this was working before the reinstall. a few versions
>>> of solaris ago there was a screen where it asked
>>> whether you wanted tight or old-fashioned levels of
>>> security. and there was a way to swap between
>>> those two -- a script in /sbin IIRC. well, i can't
>>> find that script. i don't think i was asked that
>>> question during install. or if i was asked, i
>>> blundered past it.
>>> where do i start checking?
>>> thanks in advance.
>>> j.
>> sorry. meant to include this:
>> jgs# routeadm -p
>> ipv4-routing persistent=disabled default=disabled current=disabled
>> ipv6-routing persistent=disabled default=disabled current=disabled
>> ipv4-forwarding persistent=enabled default=disabled current=enabled
>> ipv6-forwarding persistent=disabled default=disabled current=disabled
>> ipv4-routing-daemon persistent="" default=""
>> ipv4-routing-daemon-args persistent="" default=""
>> ipv4-routing-stop-cmd persistent="" default=""
>> ipv6-routing-daemon persistent="" default=""
>> ipv6-routing-daemon-args persistent="" default=""
>> ipv6-routing-stop-cmd persistent="" default=""
>> routing-svcs persistent="route:default ripng:default"
>> default="route:default ripng:default"
>
> okay, looks like i'm close to getting it sorted. i was
> looking for the wrong script name. the correct name
> is
> netservices
>
> and this fixed my problem for the moment:
>
> netservices open
>
> sorry to bother you. i'd been chasing this for
> a couple of days with no luck. finally changed
> what i was searching in google and found the
> hint in some old install instructions.
>
> any opinions on how dangerous it is to run
> w/ netservices open vs. netservices limited ?
>
> j.

It depends! What sort of a network are you connected to? What sort of
a firewall do you have. Is your network physically secure?

How big a problem is it if some outsider is able to read your network
traffic? Do you trust everyone who has access to the local network?

Etc, etc, etc. . . . .

From: hume.spamfilter on 7 Apr 2010 09:10
jay <gl(a)arlut.utexas.edu> wrote:
> i've tried the DISPLAY variable in all
> combinations of the hostname:0.0
> fqdn:0.0 and every user on every other system fails.
> even doing an su to root, and trying xclock fails.

The access list on the X server or the DISPLAY variable doesn't really
mean anything, because X simply doesn't have the TCP port open.

Undo your "netservices open" with "netservices limited", it's unnecessary
and a bad idea if you don't know what you're getting into.

Then, follow this recipe:

http://saifulaziz.wordpress.com/2009/04/03/solaris-10-remote-x11-or-cde-login-problem/

Is there a reason you can't use SSH X-forwarding?

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
 |  Next  |  Last
Pages: 1 2
Prev: Infiniband install
Next: problem with mirrored root