Loading Profile...
MS Windows Network drives fail once SftpDrive connects
I am running windows xp (sp2) and have several drive letters mapped to a debian linux samba server (mine). Every thing runs smoothly in all apps.
When I open SftpDrive and connect to another linux server (work), I run into problems
Browsing the samba connections in explorer.exe works just fine.
Doing a "net use" from the command prompt looks fine for both types of mappings.
From the command prompt I can switch to the SftpDrive mapping just fine.
However, trying to switch to the samba drives from the command propert fails with an error mesage of "The system cannot find the drive specified."
I have verified this on the only two windows xp machines I have installed the SftpDrive trial version on.
Anything further requires a reboot.
After I "disconnect" the SftpDrive, I still cannot access the drive
After I quit SftpDrive, I still cannot access the drive
I can "net use /del [drive]" succesfully, but the drive does not disappear until I reboot.
As another test, I created a drive mapping between my two workstations. This connection works just fine. Note: I was connected to SftpDrive at the time. I disconnected the SftpDrive map, quit, reconnected, and tried to access the XP mapping. It continues to work.
As another test, while connected with SftpDrive, I tried mapping a new samba connection. This worked and I have command prompt access. But the samba mappings which were open first, still do not work. So order matters. Disconnect SftpDrive map, quit, reconnect, and the new samba mapping stops working.
-Terry
When I open SftpDrive and connect to another linux server (work), I run into problems
Browsing the samba connections in explorer.exe works just fine.
Doing a "net use" from the command prompt looks fine for both types of mappings.
From the command prompt I can switch to the SftpDrive mapping just fine.
However, trying to switch to the samba drives from the command propert fails with an error mesage of "The system cannot find the drive specified."
I have verified this on the only two windows xp machines I have installed the SftpDrive trial version on.
Anything further requires a reboot.
After I "disconnect" the SftpDrive, I still cannot access the drive
After I quit SftpDrive, I still cannot access the drive
I can "net use /del [drive]" succesfully, but the drive does not disappear until I reboot.
As another test, I created a drive mapping between my two workstations. This connection works just fine. Note: I was connected to SftpDrive at the time. I disconnected the SftpDrive map, quit, reconnected, and tried to access the XP mapping. It continues to work.
As another test, while connected with SftpDrive, I tried mapping a new samba connection. This worked and I have command prompt access. But the samba mappings which were open first, still do not work. So order matters. Disconnect SftpDrive map, quit, reconnect, and the new samba mapping stops working.
-Terry
I’m disappointed
9
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Terry - thanks for this. Let me run your test scheme
-
Inappropriate?Any updates on this issue?
-Terry -
Inappropriate?Are there DFS shares on the machine in question?
-
Inappropriate?There are no windows servers in my configuration at all. Windows XP workstations connecting to linux servers via samba, sftp, or SSH. There are no permanent windows to windows mappings. In fact, the only non-default windows share is a printer queue on my primary windows workstation which hardly ever gets used/mapped.
-
Inappropriate?I have the exact same problem on a computer accessing a Ubuntu Linux samba server. The Computer in question - a laptop running Windows XP - does not belong to the domain of the Samba server, by the way. I mentioning this because I tested a similar setup with a desktop computer that belonged to the domain of another Samba server. In both cases, the drive letters are mapped persistently so that they show up after boot; SftpDrive is started when needed. On the Laptop the drive letters stop working, on the desktop machine, nothing happens to the samba drives. -
Inappropriate?Having the same issue here .. cannot run SFTPDrive without having DFS-root unavailable on domain.
I’m sad (and wondering about an update)
2 Comments
Add a comment
This solves the problem
-
hans - would it be possible to get a test login or do some interactive debugging with you? i'm not entirely sure how to replicate the issue with the DFS -
Hi Jeff
sorry for my late reply: i didnt notice your question.
It's unfortunately not possible to do interactive debugging since the issue is on my work-network which is restricted to employees.
Maybe i can give you the info you need? -
Inappropriate?Hi there i am running a Fedora server using samba as well i have a user who is running win XP pro and after she reboots her machine the network drives disconnect some of them you can double clcick on and you can explore the drives but others she has to put in here user name and password this is after she has had a new desktop but her origanle never had this problem so can any body help1 Comment Add a comment
This solves the problem
-
Marcel - can you email support@expandrive.com with a bit more info, I'd love to help out
-
Inappropriate?I have the same problem: Running awindows xp-System with connected network drives on a samba (ver. 3.0.23) Fileserver, the network drives are ok. After starting sftpdrive, I see the network drives in the explorer, but not in the file-select-box, when e.g. starting a download or a upload.
-
Inappropriate?Sorry - I have send two Emails regarding this problem to support@expandrive.com, I never get an answer. Whats going on?
-
-
Inappropriate?I think we've got this fixed now
Can you try the latest beta of ExpanDrive for Windows [rebranded SftpDrive]?
Thanks!
http://www.expandrive.com/expandrive/...
-Jeff3 Comments Add a comment
This solves the problem
-
Hi Jeff
had some problems with your mail (google mail always marks mails from SFTPdrive as being:
"Warning: This message may not be from whom it claims to be. Beware of following any links in it or of providing the sender with any personal information"
Downloaded and installed; all went well.
Unfortunately, I'm unable to register my license code I had for sftpdrive since the new version requires an 'expandrive license file' instead of a single code.
so running in evaluation mode:
* working speed appears to be improved (very nice!)
* so far, my shares still exists and I'm still able to use my company's dfs-root system (even including getting folders' properties!): Great so far.
I'll continue testing and inform you.
Maybe you can inform me about how to enter my sftpdrive license code into the new beta version?
Cheers
Hans -
Hans - We'll have a page up soon to convert your license code.
re; "this message may not be from who it claims to be" - what specific email from SftpDrive got flagged with that by google? -
Hi Jeff
great, i'll keep my eye on the license-convert page.
Many msgs sent by [noreply.expandrive@getsatisfaction.com] are marked.
Not all though strangely enough but let's say 75% including your latest was, for instance.
Guess it's because the sender is claiming to be mailing as [@getsatisfaction.com] but in real it's done by way of textdrive.com] -
Inappropriate?Hi Jeff
any idea when the page to convert the license code will be up?
(i'm halfways the trial period although i do have a license for sftpdrive)
EMPLOYEE
