Re: QNTC and Domain Shares ? -- MIDRANGE-L

Subject: Re: QNTC and Domain Shares ?
From: rob@xxxxxxxxx
Date: Mon, 10 Dec 2012 13:03:48 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Try this:
On your PC (or some other PC that is NOT a domain controller) create a
share. Then see if
WRKLNK '/QNTC/thatpc/thatshare' works. What I am finding out is that
QSECOFR can see shares on PC's that are not domain controllers but not
shares on PC's that ARE domain controllers. For example, I can access my
pc (GDL164) and GDSNT (a popular server here that is not a domain
controller) but not GDSDNS nor ARDNT (which are domain controllers). Our
Windows guy said he'll open up a ticket with IBM but he has some other
priorities first. I'm ok with that. Getting the electronics set up for
the company Christmas carry-in a few days out takes priority. I really
only use QSECOFR this way once a quarter.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QNTC and Domain Shares ? , fbocch2595
Re: QNTC and Domain Shares ? , rob

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.