In article <hWeic.270$Ja.2512078@news-text.cableinet.net>,
This works now <reply@This-works-now.com> wrote:
  [ ... ]

The simple bit I missed was sharing the "SETI Queue" directory. I'd already
shared the "C drive", where the "SETI Queue" directory was, but it seems
that that only gives access to the root of C and not to any directories
"underneath".

Share permissions and NTFS permissions interact; you can share something
with full sharing permissions (the evil default, "Full Control for Everyone")
and leave it invisible and inaccessible due to NTFS permissions.

So, once sharing for the SETI Queue directory was enabled ...."bingo - it
worked...")

Considering that SETI Queue doesn't depend upon either sharing or NTFS
permissions, I'm a bit puzzled. Both my SETI Queue systems are running
Win98, and they're working fine with nothing shared.

If this system is visible to the Internet, you should unshare C:\.
  [ ... ]

I don't s'pose you can help with connecting an NT4 workstation to the same
SETI Queue????

(I can "see" the "SETI Queue" directory on the NT4 Server, via "Network
Neighbourhood", and indeed can even use the web browser to look at the SETI
Queue stats etc. But I cannot get a WU to download into the SETI driver on
the NT4 workstation).

Is it another one of these "admin" settings??? Have tried a few things, but
keep going around in circles....!

  [ ... ]

Run the client manually on the workstation and see what error you get. It
could be something as simple as not having write permissions on the
directory.

So far as I know, nothing in SETI Queue depends upon any Windows sharing
permissions for communication; if you can ping the server from the
workstation and whatever user you're running SETI as has write/modify
permissions in the directory, SETI Queue should work. 


Gary

-- 
Gary Heston  gheston@hiwaay.net 

Contrary to popular opinion, _not_ everyone loves Raymond.