| Date: | Thu, 16 May 2002 08:40:40 -0400 |
| Reply-To: | Michael Raithel <RAITHEM@WESTAT.COM> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | Michael Raithel <RAITHEM@WESTAT.COM> |
| Subject: | Re: SAS Server can't access network drives |
| Content-Type: | text/plain; charset="iso-8859-1" |
|---|
Dear SAS-L-ers,
Simon Gillow posted, in part:
<<Simon's entire posting can be found beneath the Sig. line>>
>The problem is we have a new SAS server running SAS v8.2 on an NT Server
using
>SAS/CONNECT. We also have SAS 8.2 and SAS/CONNECT on the client PCs.
Despite
>lots of trying we can't get remote submitted code to see network drives.
>
Simon, your posting has presented me with a very timely, almost unparalleled
opportunity to engage in self promotion and gross personal aggrandizement:-)
<<I will borrow one of Bill V.'s "VBG"s, and post it here>> While I cannot
offer a specific solution to your problem, I can point you at a piece of
code that you can run to quickly determine exactly which disk drives your
remote SAS sessions _ACTUALLY_CAN_ "see". That code can be found under
Quick Tips on the SAS Institute's Web pages at the following URL:
http://www.sas.com/service/techtips/quicktips/drives_0402.html
I'll bet that this code (minus the PROC FSLIST) will come in handy during
your testing phases, as you attempt to determine whether changes you made
have had any effect on your remote session's ability to see disk drives.
Simon, best of luck to you in your effort to get your remote SAS sessions to
open their eyes to the network world that surrounds them!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect
those of my organization or my associates. All SAS code and/or
methodologies specified in this posting are for illustrative purposes only
and no warranty is stated or implied as to their accuracy or applicability.
People deciding to use information in this posting do so at their own risk.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Michael A. Raithel
"The man who wrote the book on performance"
E-mail: MichaelRaithel@westat.com
Author: Tuning SAS Applications in the MVS Environment
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
...don't you fret, don't you fear, I will bring you good
cheer... -- Jethro Tull
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
<<Simon's entire posting:>>
Hello all,
We have had a support call with SI outstanding for ages as to how to solve
these problems, we have tried numerous different ways and have had support
from
SAS in the UK and in Cary but no-one has managed to solve the problem yet so
I
am opening it up to you guys and gals.
The problem is we have a new SAS server running SAS v8.2 on an NT Server
using
SAS/CONNECT. We also have SAS 8.2 and SAS/CONNECT on the client PCs. Despite
lots of trying we can't get remote submitted code to see network drives.
We have tried numerous methods including NET USE commands, giving me
administrator rights, telnetting to the server, applying a hotfix, etc.
It is my opinion that our secured spawner (installed using spawner -i -c tcp
-security -authserver nbas04 -z) isnt logging me in properly as although I
do
have rights to see a certain network drive from my local PC, when I remote
submit that same code it says that I do not have sufficient authorization to
access that drive.
We have looked on the Techincal Support area of SAS.com and found that the
following note says that it isnt possible to
use SSPI for transparent authentication.
http://www.sas.com/service/techsup/unotes/SN/003/003095.html Has anyone
managed to access network drives through a remote SAS session?
Any hints/tips would be gratefully received (before I tear all my hair out).
If
you need any more information in order to help me
please let me know.
Thanks,
Simon
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
Bradford & Bingley plc
Registered Office: PO Box 88, Croft Road, Crossflatts, Bingley, West
Yorkshire, BD16 2UA
Registered in England No. 3938288
Regulated by the Financial Services Authority and a Member of the General
Insurance Standards Council.
http://www.bbg.co.uk
Bradford Bingley plc
**********************************************************************
|