Re: Comet 2006.361- CFAM & Security Server Problems


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Jim Guerber on October 30, 2005 at 09:04:59:

In Reply to: Comet 2006.361- CFAM & Security Server Problems posted by Bruce on October 28, 2005 at 22:52:43:

WOW, I know the answer to this one, but I don't know how to explain it!!! but, I will try....

The file server runs in 2 modes. The first way is as a shared server. This is the traditional way the server runs. It serves files to multiple nodes that connect to it via tcp/ip. This requires a Server license.

When we designed CFAM, we wanted a way to use the same server code to make local files work. We devised a SECOND way to connect CFAM to the File Server This is for private files. The directories are still configured as type C. CFAM is still used. But there is NO LICENSE REQUIRED.

The problem is that you are set up to use the shared server even though you only want to get access to your own files.

How do you tell Comet that this is what you want?? Take the C out of the server statement for the node!

Not

Server = N00,SC;

but

Server = N00,S;

Everything else in your INI file should remain the same, in particular, each directory should be configured as a type C.




Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):






[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]