|
I'm not sure, but I think the home drive mapping gets applied, so if you specify a map of drive H in active directory that may work. OR... How are you executing the transfer? Can you execute a map command first? You can map a drive using: Net use h: \\server\share So if you can execute the above command and then execute the transfer that should work. Oh, and to delete use: Net use h: /delete -Walden ------------ Walden H Leverich III President & CEO Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ian Dorrington Sent: Tuesday, 26 October, 2004 12:16 To: 'Midrange Systems Technical Discussion' Subject: RE: Using Client Access to connect to a windows 2003 server Thanks that worked a treat. We're migrating from an old server so all our transfers reference the H: drive (quite a few of them). So I'll get our network guys to work how to map a drive for the different log on session, if that's possible. Ian www.greeneking.co.uk -----Original Message----- From: Walden H. Leverich [mailto:WaldenL@xxxxxxxxxxxxxxx] Sent: Tuesday, October 26, 2004 4:15 PM To: Midrange Systems Technical Discussion Subject: RE: Using Client Access to connect to a windows 2003 server >The client access server is running >under the same user as the server is logged on as. Yes, but it's running in a different login session, so it doesn't have the mapped drives you have. Try replacing the H: with the UNC reference, for example \\fs1\sharedfiles\ABC\kitsent.xls (where \\fs1\sharedfiles) is the server and share name for the remote server. -Walden ------------ Walden H Leverich III President & CEO Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. ********************************************************************** The contents of this E Mail message are confidential as between the sender and the named recipient, and may be legally privileged. Any person receiving this E Mail message not being the named recipient is prohibited from using the contents for any purpose other than to pass it to the named recipient without copying, disclosing or disseminating the contents in any way other than with the express consent of the named recipient. Greene King reserves the right to monitor any and all E Mail communications using any part of its Network. This footnote also confirms that this email message has been swept by MIMEsweeper/Sophos for the presence of computer viruses. ********************************************************************** -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.