SYS0065: Network access is denied.

[Keith Marjerison]

Hello All;
I have a system with eCS 2.0 RC6 installed on it. I have tried every
version of Samba server and all installs work. This machine has no
problem sharing.
I have also tried installing all available versions of Samba Client for
eComStation, and although all versions can see all of the smb shares on
my network, none of these versions can connect to a share.
I get the same results when using the latest Netdrive and samba plugin.
In all cases the drives attach but when I try to open one, I get an
error that there are no objects found to display. If I navigate to the
share from a command prompt I get this:
SYS0065: Network access is denied.
I have tried adding different users and passwords, but always the same
result.
I had no problems, other than the 2G limit, when connecting to these
shares with Netbios over TCP/IP.
Any ideas would be greatly appreciated.
Thanks in advance.

[Pete Brown]

Hi Keith

Post by Keith Marjerison
Hello All;
I have a system with eCS 2.0 RC6 installed on it. I have tried every
version of Samba server and all installs work. This machine has no
problem sharing.
I have also tried installing all available versions of Samba Client for
eComStation, and although all versions can see all of the smb shares on
my network, none of these versions can connect to a share.
I get the same results when using the latest Netdrive and samba plugin.
In all cases the drives attach but when I try to open one, I get an
error that there are no objects found to display. If I navigate to the
SYS0065: Network access is denied.
I have tried adding different users and passwords, but always the same
result.
I had no problems, other than the 2G limit, when connecting to these
shares with Netbios over TCP/IP.
Any ideas would be greatly appreciated.
Thanks in advance.

I've had the "SYS0065: Network access is denied." problem and reading
through the thread "Re: samba server samba-1-0-3.wpi problems" I
refreshed my memory of how I "cured" it here.

Basically Uninstall samba server and then hunt down every samba server
related file on your hard drive - make sure you check the %TEMP%
location - and delete them prior to reInstalling samba server.

Regards

Pete

[Keith Marjerison]

Post by Pete Brown
Hi Keith

Post by Keith Marjerison
Hello All;
I have a system with eCS 2.0 RC6 installed on it. I have tried every
version of Samba server and all installs work. This machine has no
problem sharing.
I have also tried installing all available versions of Samba Client for
eComStation, and although all versions can see all of the smb shares on
my network, none of these versions can connect to a share.
I get the same results when using the latest Netdrive and samba plugin.
In all cases the drives attach but when I try to open one, I get an
error that there are no objects found to display. If I navigate to the
SYS0065: Network access is denied.
I have tried adding different users and passwords, but always the same
result.
I had no problems, other than the 2G limit, when connecting to these
shares with Netbios over TCP/IP.
Any ideas would be greatly appreciated.
Thanks in advance.

I've had the "SYS0065: Network access is denied." problem and reading
through the thread "Re: samba server samba-1-0-3.wpi problems" I
refreshed my memory of how I "cured" it here.
Basically Uninstall samba server and then hunt down every samba server
related file on your hard drive - make sure you check the %TEMP%
location - and delete them prior to reInstalling samba server.
Regards
Pete

Hello Peter;
Just to be sure, this IS NOT a Samba Server problem, I am unable to to
open shares using EVFSGUI or Netdrive to access Samba shares.
Any way, I tried your advice and un-installed Samba Server as well as
EVFSGUI and the original esambac. I then re-installed fresh, and I still
have the same results, no connection.
It appears that the original esambac.wpi installs into \ecs\bin and you
can't change this, installing any EVFSGUI wpi packages even with esambac
installed puts those files in \samba and you can't change this.
Anyone know why a wpi package does not recognize where previous
versions where installed? Does Warpin not check this before installing?
Why would a newer version of the same packages not install in the same
place?
Anymore ideas would be greatly appreciated.
Thanks in advance.

[Herwig Bauernfeind]

Post by Keith Marjerison

Post by Pete Brown
Hi Keith

Post by Keith Marjerison
Hello All;
I have a system with eCS 2.0 RC6 installed on it. I have tried every
version of Samba server and all installs work. This machine has no
problem sharing.
I have also tried installing all available versions of Samba Client for
eComStation, and although all versions can see all of the smb shares on
my network, none of these versions can connect to a share.
I get the same results when using the latest Netdrive and samba plugin.
In all cases the drives attach but when I try to open one, I get an
error that there are no objects found to display. If I navigate to the
SYS0065: Network access is denied.
I have tried adding different users and passwords, but always the same
result.
I had no problems, other than the 2G limit, when connecting to these
shares with Netbios over TCP/IP.
Any ideas would be greatly appreciated.
Thanks in advance.

I've had the "SYS0065: Network access is denied." problem and reading
through the thread "Re: samba server samba-1-0-3.wpi problems" I
refreshed my memory of how I "cured" it here.
Basically Uninstall samba server and then hunt down every samba server
related file on your hard drive - make sure you check the %TEMP%
location - and delete them prior to reInstalling samba server.
Regards
Pete

Hello Peter;
Just to be sure, this IS NOT a Samba Server problem, I am unable to to
open shares using EVFSGUI or Netdrive to access Samba shares.
Any way, I tried your advice and un-installed Samba Server as well as
EVFSGUI and the original esambac. I then re-installed fresh, and I still
have the same results, no connection.

You have to enable logging on the client and on the server side, set
loglevel to 5. This will reveal why things go wrong.

Post by Keith Marjerison
It appears that the original esambac.wpi installs into \ecs\bin and you
can't change this, installing any EVFSGUI wpi packages even with esambac
installed puts those files in \samba and you can't change this.
Anyone know why a wpi package does not recognize where previous
versions where installed? Does Warpin not check this before installing?
Why would a newer version of the same packages not install in the same
place?

The Commandline utilities were hardcoded to install into \samba, the
evfsgui stuff still goes into ecs\bin.
Future WPI will put the commandline utility stuff into \ecs\system\samba.

Regards,
Herwig

[Keith Marjerison]

Post by Herwig Bauernfeind

Post by Keith Marjerison

Post by Pete Brown
Hi Keith

Post by Keith Marjerison
Hello All;
I have a system with eCS 2.0 RC6 installed on it. I have tried every
version of Samba server and all installs work. This machine has no
problem sharing.
I have also tried installing all available versions of Samba Client for
eComStation, and although all versions can see all of the smb shares on
my network, none of these versions can connect to a share.
I get the same results when using the latest Netdrive and samba plugin.
In all cases the drives attach but when I try to open one, I get an
error that there are no objects found to display. If I navigate to the
SYS0065: Network access is denied.
I have tried adding different users and passwords, but always the same
result.
I had no problems, other than the 2G limit, when connecting to these
shares with Netbios over TCP/IP.
Any ideas would be greatly appreciated.
Thanks in advance.

I've had the "SYS0065: Network access is denied." problem and reading
through the thread "Re: samba server samba-1-0-3.wpi problems" I
refreshed my memory of how I "cured" it here.
Basically Uninstall samba server and then hunt down every samba server
related file on your hard drive - make sure you check the %TEMP%
location - and delete them prior to reInstalling samba server.
Regards
Pete

Hello Peter;
Just to be sure, this IS NOT a Samba Server problem, I am unable to to
open shares using EVFSGUI or Netdrive to access Samba shares.
Any way, I tried your advice and un-installed Samba Server as well as
EVFSGUI and the original esambac. I then re-installed fresh, and I still
have the same results, no connection.

You have to enable logging on the client and on the server side, set
loglevel to 5. This will reveal why things go wrong.

Post by Keith Marjerison
It appears that the original esambac.wpi installs into \ecs\bin and you
can't change this, installing any EVFSGUI wpi packages even with esambac
installed puts those files in \samba and you can't change this.
Anyone know why a wpi package does not recognize where previous
versions where installed? Does Warpin not check this before installing?
Why would a newer version of the same packages not install in the same
place?

The Commandline utilities were hardcoded to install into \samba, the
evfsgui stuff still goes into ecs\bin.
Future WPI will put the commandline utility stuff into \ecs\system\samba.
Regards,
Herwig

Hello Herwig;
I have upgraded my Netdrive samba plugin, and now I can connect to
samba shares using Netdrive. This works well enough for my purposes so I
am going to wait for the eCS 2.0 release to see if I can get EVFSGUI
working.
Thanks for the help.