| Author |
Message |
tochill
Guest
|
 Posted: Wed Nov 06, 2013 1:20 am Post subject: |
 |
|
| TGRMN Software wrote: | | Hi, could you write to support@tgrmn.com , I'll see if we can send you a special version of ViceVersa to debug this issue and collect more info on why it's failing. thanks! |
I figured out the issue. it was the implementation of SMB2 within mavericks. i disabled it in windows 7 which forces it to connect via SMB1... its a short turn workaround until they fix mavericks.
support. microsoft .com/kb/2696547
To disable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled |
|
| Back to top |
|
 |
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8758
|
|
| Back to top |
|
|
Trailerman
Joined: 26 Aug 2005
Posts: 26
|
| Posted: Wed Nov 06, 2013 9:00 am Post subject: |
|
|
| tochill wrote: |
I figured out the issue. it was the implementation of SMB2 within mavericks. i disabled it in windows 7 which forces it to connect via SMB1... its a short turn workaround until they fix mavericks.
support. microsoft .com/kb/2696547
To disable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled |
Hi Tochill
Sounds like you might be onto something, but for some reason it's making no difference here.
Just so I'm clear, those two commands need to be run on the VV Pro client system (Windows 7 in our case), and this should force an SMB1 connection - is that correct?
Do I need a reboot after running those commands (I presume they can just be run in a CMD window)?
Thanks for any further help. Would be great to find a quick workaround.
Jules |
|
| Back to top |
|
|
Trailerman
Joined: 26 Aug 2005
Posts: 26
|
| Posted: Wed Nov 06, 2013 9:17 am Post subject: |
|
|
| Scratch that. Works fine after reboot ... so far. Great news. |
|
| Back to top |
|
|
tochill
Guest
|
| Posted: Wed Nov 06, 2013 4:40 pm Post subject: |
|
|
Glad it worked, i am not sure its something Vice Versa could fix. i tried a few other sync programs and they all run into the same issue. I think it has to do with the way it scans the drive.
Probably should have mentioned the reboot  |
|
| Back to top |
|
|
Trailerman
Joined: 26 Aug 2005
Posts: 26
|
| Posted: Wed Nov 06, 2013 6:16 pm Post subject: |
|
|
 No worries!
Thanks for figuring this out. |
|
| Back to top |
|
|
|
ViceVersa HOME 
Forum FAQ
Search Forum
Register
Profile
Log in
