[clue] 'Export display' question

Fri Feb 28 08:02:18 MST 2014

In relation to the X11 forwarding issue I know that I've had trouble with
it over VPN before.  When I last had that problem it was due to a
difference in framing between the networks, I had to set the framing down
to something like 1300 on either end before it would work.  I know that was
mostly a problem with the GRE tunnel that it was using, but you might look
into that.  If you run wireshark on the connection you won't be able to see
the packets themselves but you'll see a lot of retran and rst traffic.

On Thu, Feb 27, 2014 at 6:18 PM, <foo7775 at comcast.net> wrote:

> You're absolutely right, the X11 issue was tangential.  While I wasn't
> able to solve the "export display" issue, I *was* successful in figuring
> out how to get that specific printer driver installed manually, & getting
> the printer working *without* using the setup routine (kind of an
> "end-around" if you will).
>
> Big thanks for the replies Quentin/Chris, I'm going to read the info in
> the links you've posted & see if I can't learn a bit more...
>
> T.
> ------------------------------
> *From: *"Chris Fedde" <chris at fedde.us>
> *To: *"CLUE's mailing list" <clue at cluedenver.org>
> *Sent: *Thursday, February 27, 2014 3:17:31 PM
> *Subject: *Re: [clue] 'Export display' question
>
> I've had pretty good results using IPP or "jet direct" to the 9100 port
> and the generic PCL6 drivers or postscript for similar printers. Try
> connecting to the printers ip with a browser and see if it'll give you any
> clues.
>
> While solving the X11 issue is fun it seems tangential to the real problem
> you are having.
>
>
> On Thu, Feb 27, 2014 at 10:36 AM, Quentin Hartman <qhartman at gmail.com>wrote:
>
>> Oh, and you'll probably need xauth and xvfb installed on the Linux box to
>> get x forwarding working.
>>
>> This page has a discussion that might be relevant, if you haven't already
>> found it:
>>
>>
>> http://unix.stackexchange.com/questions/76113/x11-forwarding-not-working-from-putty-and-xming-to-centos-6-4
>>
>>
>> On Thu, Feb 27, 2014 at 10:25 AM, <foo7775 at comcast.net> wrote:
>>
>>> Thank you Quentin, it's worth a try.  Will update with results.
>>>
>>> T.
>>> ------------------------------
>>> *From: *"Quentin Hartman" <qhartman at gmail.com>
>>> *To: *"CLUE's mailing list" <clue at cluedenver.org>
>>> *Sent: *Thursday, February 27, 2014 10:14:59 AM
>>> *Subject: *Re: [clue] 'Export display' question
>>>
>>>
>>> According to
>>> http://www.sharpusa.com/ForBusiness/DocumentSystems/MFPsPrinters/MXM503.aspxthat printer claims to support PCL6 and may support Postscript, so you
>>> could try using a generic PCL or Postcript driver using a standard port
>>> 9100 network printer config. It may "just work". I've done that countless
>>> times to get "unsupported" printers to work in Linux. You lose some of the
>>> fancier options, but they spit out pages just fine.
>>>
>>>
>>> On Thu, Feb 27, 2014 at 9:39 AM, <foo7775 at comcast.net> wrote:
>>>
>>>> Hi guys, I have a problem with a serious time component.
>>>>
>>>> Trying to run a Sharp printer install routine on a "cmdline-only" RHEL
>>>> 6.4 system *(no Xwindows installed)*.  My connection is via SSH over
>>>> PuTTY from my Win7 workstation *(through a VPN)*.  When I run ./setup,
>>>> the routine returns 'Can't open display'.  I've enabled X11 forwarding
>>>> within PuTTY, and entered "<wkstn IP addr>:0.0" in the 'X display location'
>>>> blank.  Also tried it with "<wkstn IP addr>:0", same result.
>>>>
>>>>   One popular suggestion that I've found on many pages is to enter
>>>> 'xhost +' at the command line - but since this server doesn't have X
>>>> installed, there is no xhost.
>>>>
>>>>   I've then installed Xming on my workstation, configured it as per
>>>> www.nth-design.com/2010/05/19/x11-putty-xming/ precisely.
>>>>
>>>> Wasn't quite sure if I had to make a corresponding change on the
>>>> server, so I tried entering "export display <wkstn IP addr>:0.0" on the
>>>> RHEL box, then running setup again.  No luck.  Also tried it with "export
>>>> display <wkstn IP addr>:0", same result.
>>>>
>>>> Looked around for a bit more information, found this page (
>>>> http://www.doxer.org/learn-linux/use-xming-xshell-to-display-linux-gui-to-windows-desktop-x11-forwarding/)
>>>> which changed the observed behavior a bit - *now* when I run setup, it
>>>> pauses for maybe 20-30 seconds before returning the 'Can't open display'
>>>> error *(which leads me to suspect that at least the server-side of the
>>>> equation might be working correctly now)*.
>>>>
>>>> The setup routine is a binary, so it's opaque to me.
>>>>
>>>> X11 forwarding is enabled within the sshd_config file.
>>>> /var/log/messages contains no entries from today.
>>>>
>>>> The Windows firewall has an exception to allow XMing via the 'Private'
>>>> network types, but *not* through domain types, so that could be an issue *(I'm
>>>> currently unable to toggle that, suspect it's managed by either the
>>>> security team or 'desktops/wkstn' team)*.  (I've sent an email to the
>>>> company directors who are emphasizing the time pressure, with any luck
>>>> they'll be able to get me past *that* speed bump.)
>>>>
>>>> The Xming log contains this snippet, which *seems* to indicate that it
>>>> thinks that everything on my Win7 box is OK:
>>>>
>>>> winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
>>>> winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
>>>> winProcEstablishConnection - Hello
>>>> winInitClipboard ()
>>>> winProcEstablishConnection - winInitClipboard returned.
>>>> winClipboardProc - Hello
>>>> DetectUnicodeSupport - Windows Vista
>>>> winClipboardProc - DISPLAY=127.0.0.1:0.0
>>>> winMultiWindowXMsgProc - XOpenDisplay () returned and successfully
>>>> opened the display.
>>>> winInitMultiWindowWM - XOpenDisplay () returned and successfully opened
>>>> the display.
>>>> winClipboardProc - XOpenDisplay () returned and successfully opened the
>>>> display.
>>>>
>>>>
>>>> To be quite honest, I *don't care* about running the setup routine, if
>>>> I could get the printers installed another way - but the foomatic info that
>>>> I've seen this server doesn't list a Sharp MX-503N, & I haven't been able
>>>> to find any other, compatible models that I could try.
>>>>
>>>> I'd sure be grateful for any help/suggestions, etc.  TIA.
>>>>
>>>> T,.
>>>>
>>>> _______________________________________________
>>>> clue mailing list: clue at cluedenver.org
>>>> For information, account preferences, or to unsubscribe see:
>>>> http://cluedenver.org/mailman/listinfo/clue
>>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list: clue at cluedenver.org
>>> For information, account preferences, or to unsubscribe see:
>>> http://cluedenver.org/mailman/listinfo/clue
>>>
>>> _______________________________________________
>>> clue mailing list: clue at cluedenver.org
>>> For information, account preferences, or to unsubscribe see:
>>> http://cluedenver.org/mailman/listinfo/clue
>>>
>>
>>
>> _______________________________________________
>> clue mailing list: clue at cluedenver.org
>> For information, account preferences, or to unsubscribe see:
>> http://cluedenver.org/mailman/listinfo/clue
>>
>
>
> _______________________________________________
> clue mailing list: clue at cluedenver.org
> For information, account preferences, or to unsubscribe see:
> http://cluedenver.org/mailman/listinfo/clue
>
> _______________________________________________
> clue mailing list: clue at cluedenver.org
> For information, account preferences, or to unsubscribe see:
> http://cluedenver.org/mailman/listinfo/clue
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cluedenver.org/pipermail/clue/attachments/20140228/182efca3/attachment.html 