Koozali.org: home of the SME Server

Backup2ws Problem won't connect to network share

Offline sits

  • ***
  • 68
  • +0/-0
Backup2ws Problem won't connect to network share
« on: May 23, 2004, 08:27:35 AM »
Hello,

I have installed Darrell May's Backup2ws rpm on my SME 6.03 and can't to work, I have created a share on a windows 2000 Server wih permissions set to everyone and security set to everyone and I can access the share from other windows machines on the network, but when I run the backup job I get this in my messages log:

May 23 15:37:01 e-smith e-smith-bg: 5703: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
May 23 15:37:01 e-smith e-smith-bg: SMB connection failed
May 23 15:37:01 e-smith e-smith-bg: Error occured mounting //sandgate/test at /sbin/e-smith/backup2ws-backup line 64.

I have setup a backup user with full permissions, I can ftp into the backup folder
Any and all help is welcome
...

Offline raem

  • *
  • 3,972
  • +4/-0
Backup2ws Problem won't connect to network share
« Reply #1 on: May 23, 2004, 04:31:48 PM »
Can you browse using Windows Explorer to that backup share on the workstation ?

Have you put a login name and password for that share in the backup2ws job ?
...

k_graham

Re: Backup2ws Problem won't connect to network share
« Reply #2 on: May 26, 2004, 06:09:57 AM »
Quote from: "sits"
Hello,

I have installed Darrell May's Backup2ws rpm on my SME 6.03 and can't to work, I have created a share on a windows 2000 Server wih permissions set to everyone and security set to everyone and I can access the share from other windows machines on the network, but when I run the backup job I get this in my messages log:

May 23 15:37:01 e-smith e-smith-bg: 5703: session setup failed: ERRDOS - ERRnoaccess (Access denied.)
May 23 15:37:01 e-smith e-smith-bg: SMB connection failed
May 23 15:37:01 e-smith e-smith-bg: Error occured mounting //sandgate/test at /sbin/e-smith/backup2ws-backup line 64.

I have setup a backup user with full permissions, I can ftp into the backup folder
Any and all help is welcome


Did you use the backup2ws for 6 and not 5
Quote

Unfortunately Contribs org contribs section points people to the version of backup for mitel version 5. When there having clicked for the 5 version, you need to look at the directory and go up in directory hiarchy to the branch that indicates smeserver
http://mirror.contribs.org/smeserver/contribs/dmay/smeserver/6.x/beta/

Actually some should also go to dmays own site because he mentions a need to remove some stuff to do with the 5 version before installing 6 version. His site is www.myezserver.com


Also try using the ip instead of name of server \\192.168.0.1\shareddocs\bu\911

Are you using correct case for subdirectories, keep everything lowercase.

Lastly I haven't managed to get automated backups to work - have to start them manually. Beta software?

Make sure you can access directory from another computer and write to it. Try admin as a user on the computer you are writing to and keep everythin lowercase

If you only want to backup an ibay use Winrar and create a batch file on the windows machine and set the automated backup there.

Ken

felipevidal

Backup2ws Problem won't connect to network share
« Reply #3 on: May 27, 2004, 01:24:23 AM »
I had a similar error (but I think a different cause than 'sits' problem) and had a Linux guru friend check out the script and the messages log. He came to the following conclusion which, after being applied, worked like a charm.  Do NOT use backslashes in the 'Destination' field of web interface when describing the path to the Windows workstation.

NO! - \\workstation\path
YES! - //workstation/path

Good Luck,
-felipe

Offline sits

  • ***
  • 68
  • +0/-0
Backup2ws Problem won't connect to network share
« Reply #4 on: May 27, 2004, 02:26:32 AM »
Thanks for the reply's guys

Can you browse using Windows Explorer to that backup share on the workstation ?

Have you put a login name and password for that share in the backup2ws job ?

 I can browse the network to this share.
 I have used login name and password

Did you use the backup2ws for 6 and not 5

 Yes I am using backup2ws for 6

Also try using the ip instead of name of server \\192.168.0.1\shareddocs\bu\911

 I will try using the IP instead. but I can ping the NT server name from SME
 This didn't work either.

NO! - \\workstation\path
YES! - //workstation/path

 I already use Forward slashes.

I seem to be at a loss, with this one, anymore ideas?
...

Offline raem

  • *
  • 3,972
  • +4/-0
Backup2ws Problem won't connect to network share
« Reply #5 on: May 27, 2004, 03:24:04 AM »
The backup2ws contrib works fine for me with automated backups on a sme 6.0 server, so it DOES work. In 2 different locations where the sme server is the domain controller, it does backups to WinXP workstation (member of the domain) and Win98 workstation (logged on to the domain).

After re-reading the thread, how about trying this.

Can you do a backup to a workstation rather than a Windows 2000 server share. Preferably a not so secure Win98 share if you have one, no issues then with domain access rights etc.

I am suspecting your sme server is not part of your Win2K Server domain and that is why access is denied.

Which server machine is your domain controller ?
...

Anonymous

Backup2ws Problem won't connect to network share
« Reply #6 on: May 27, 2004, 03:41:12 AM »
Quote from: "sits"
Thanks for the reply's guys

Can you browse using Windows Explorer to that backup share on the workstation ?

Have you put a login name and password for that share in the backup2ws job ?

 I can browse the network to this share.
 I have used login name and password

Did you use the backup2ws for 6 and not 5

 Yes I am using backup2ws for 6

Also try using the ip instead of name of server \\192.168.0.1\shareddocs\bu\911

 I will try using the IP instead. but I can ping the NT server name from SME
 This didn't work either.

NO! - \\workstation\path
YES! - //workstation/path

 I already use Forward slashes.

I seem to be at a loss, with this one, anymore ideas?


Yes it should no doubt be forward slashes - I was just changing backup to another computer and no doubt put them in wrong.

IP address  removes problem of upper and lower case.

Loginname isn't administrator which is too long for SME server.

You don't have some filter, firewall settings enabled on the Windows network setting do you.

What is local IP of Windows computer and IP of SME?

Also subnet is 255.255.255.0 on both systems?

Also if all else fails - a reboot of SME server never hurt.

Ken

rishi

Backup2ws Problem won't connect to network share
« Reply #7 on: May 28, 2004, 06:57:54 AM »
Not sure if this will help or not, just adding my 2c worth in case it helps...

I was recently having trouble with this, and the problem was caused by the way windows was showing the share when I browsed to it. It was calling the share:
Quote
//Videoserver/data

when it was really:
Quote
//videoserver/data

...note the case on the letter 'v'...

also, you can only mount the direct share, not any directories under it... For example, if //videoserver/data is the name of the share, it won't work if you try to map //videoserver/data/backups even if 'backups' is a valid folder on the share.

Hope this helps. Rishi.  :-o

zumba

Glazer & the Buccaneers
« Reply #8 on: June 19, 2004, 01:27:02 AM »
what kind of sport is this? i ve never heard about it and never seen it...
I like - football, tennis, http://www.buy-development-tool.narod.ru figure skating, extreme sports
Dislike - hockey, basketball, car racing, box and all the rest

Offline lproven

  • **
  • 27
  • +0/-0
Backup2ws Problem won't connect to network share
« Reply #9 on: August 04, 2004, 07:04:31 PM »
Just for information, this failure to connect is nothing to do with the case of names or IP addresses. It's local versus domain accounts and it's a known Samba issue.

I've discussed it more and explained how to resolve it here:

http://forums.contribs.org/index.php?topic=23382.0

Offline sits

  • ***
  • 68
  • +0/-0
backup2ws
« Reply #10 on: August 05, 2004, 03:20:26 PM »
Thanks guys
the domain/user login for the win2003 server did the trick, I created an account on the 2003 server and on the SME to suit, and now it works.
...