[FreeNX-kNX] File and Printer Sharing Failing

[Murray Trainer]

On Thu, 2005-06-23 at 08:19, Murray Trainer wrote:
> On Wed, 2005-06-22 at 22:34, Paul van der Vlis wrote:
> > Murray Trainer schreef:
> > > On Fri, 2005-06-17 at 11:16, Root at imap.central-data.net wrote:
> > > 
> > >>Hi Guys,
> > >>
> > >>I am evaluating NX client 1.4.0-103 and NX server 1.4.0-103.  I am
> > >>having problems with file sharing with some Windows XP SP2 PC's dialing
> > >>in via a modem.  I get the error below with a modem connection but the
> > >>file and printer sharing works fine via a DSL connection from the same
> > >>PC.  The network and XP firewall settings look the same for the DSL and
> > >>modem connection.  I tried the file and printer sharing via a modem from
> > >>another PC booted into NT 4.0 and it worked fine.
> > >>
> > >>Error: Mount of share 'Work' failed, reason:
> > >>2108: session request to SERVER failed (Call returned zero bytes
> > >>(EOF)2108: session request to *SMBSERVER failed (Call returned zero
> > >>bytes (EOF))
> > >>SMB connection failed
> > >>
> > >>The errors below are from /var/log/messages for the failed session.
> > >>
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: NX> 596 ERROR:
> > >>NXNODE Ver. 1.4.0-103 (Error id eF08839) [eF08839] 'main:nxnode_ee:1905'
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: NX> 596 ERROR:
> > >>Thu Jun 16 14:40:05 2005 running as user: 'gls' (uid: 501) on 'vserver'
> > >>[eF08839] 'main:nxnode_ee:1905'
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: NX> 596 ERROR: in
> > >>node SMB manager: session SMB mount [eF08839] 'main:nxnode_ee:1905'
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: NX> 596 ERROR:
> > >>Mount of share 'Work' failed, reason: [eF08839] 'main:nxnode_ee:1905'
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: NX> 596 1769:
> > >>session request to SERVER failed (Call returned zero bytes (EOF))1769:
> > >>session request to *SMBSERVER failed (Call returned zero bytes (EOF))
> > >>[eF08839] 'main:nxnode_ee:1905'
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: NX> 596 SMB
> > >>connection failed. [eF08839] 'main:nxnode_ee:1905'
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: NX> 596 init:
> > >>stdin arguments:
> > >>port=4052,username=Dean,password=******,share=Work,computername=SERVER,
> > >>session_id=B164FBC0AD9B259D5C1CF7BC3C495CEF,dir=mnt%2fgls%2fMyShares%2fWork,
> > >>display=1052'main:nxnode_ee:1905'
> > >>Jun 16 14:40:05 vserver NXNODE 1.4.0-103[1766]: ERROR: message number:
> > >>1003 was not sent: write to STDOUT failed: Broken pipe
> > >>'main:nxnode_ee:1952'
> > >>
> > >>Has anyone had the same problem or have any idea what is happening here?
> > >>Thanks
> > >>
> > >>Murray
> > > 
> > > 
> > > Today, I deleted the shared drives and printers in the NX client
> > > configuration on the XP PC and re-entered them then tried connecting
> > > with a modem and this time everything worked???  The shared folder and
> > > printer mapped fine Not sure what the problem was as the previous
> > > configuration worked fine over DSL. Maybe I had the client set to DSL
> > > speed instead of modem which caused comms issues?  I will try and
> > > reproduce the problem.
> > 
> > Maybe your DSLconnection has most ports closed in a firewall and your
> > modemconnection is open?
> > 
> > With regards,
> > Paul van der Vlis.
> 
> Hi Paul,
> 
> The firewall settings were the same for modem and DSL.  It appears that
> the NX client isn't always saving its settings when you define the
> shares.  Have a play with it and you'll notice that sometimes it doesn't
> detect that you have changed settings as the save button is still
> blanked out.  My boss was testing a bit more last night so we might be
> able to reproduce the problem.
> 
> Murray

The problem above turned out to be the share required the Domain to be
specified to connect - ie. DOMAIN\username and password to connect to it
instead of just username and password.  I then tried to connect a
printer which failed with the DOMAIN\username and password syntax.  I
then had a look at /etc/cups/printers.conf and noticed that the printers
were defined using forward slashes which is pretty standard on UNIX.  I
tried using DOMAIN/username and password to connect to my shared client
printer and it worked.  This looks like a bug as it should be entered as
Domain\username backslash to be consistent with the Domain\username
required for file sharing in the Windows client. 

In trying to trying to resolve these problems I also came across a bug
in Windows XP Service Pack 2 that could cause Access Denied type errors.
This is resolved by applying all the XP updates. The problem is
described below with links to the appropriate MS updates/hotfixes.

Murray

>All loopback addresses except 127.0.0.1 don't work with Service Pack 2.
>This may break SSL Gateways, Samba authentication, SSH port forwarding
>using these IP addresses, etc. The problem is described in the
>following Microsoft Knowledge Base article.

>Programs that connect to IP addresses that are in the loopback address
>range may not work as you expect in Windows XP Service Pack 2
>http://support.microsoft.com/kb/884020/

>Microsoft has issued a hotfix that solves this problem:

>http://www.microsoft.com/downloads/details.aspx?FamilyID=17d997d2-5034-4bbb-b74d-ad8430a1f7c8