Posted by Jim Guerber on September 15, 2005 at 10:53:45:
In Reply to: Access Comet files on Windows Server thru Novell posted by Greg Mayberry on September 15, 2005 at 07:55:30:
Hi Greg,
I understand your concerns. Here is the way you can run.
We have built CometServe as a "full service" file server. Your Comet clients do not need to "log in" to the windows 2003 server. You do not need to setup any shares on it or map any drives to it.
No connection whatsoever from the outside through your firewall (unless you have Comet running on the outside).
No SMTP
No FTP
No POP3
Here is how I would set this up:
Let's say that the Novell Server is at Address 192.168.1.100, This will be your "public" server.
And let's say the win2003 server is at 192.168.1.200, this will be where ALL your Comet Files are stored.
You would do the server install on the win2003 server.
You would do the workstation install on the Novell server.
Also do the minimal workstation install on each client.
Make a share on the Novell Server, for the Comet Executables and the cfig files (the "start in" folder).
Set up the folders on the win2003 server as so:
c:\
comet
rel
utl
cos
...
On the win2003 server, you as administrator must run comet locally to get the cfg files made with sysgen.
Copy the sample.ini file from the rel folder to a file named comet.ini in the win2003 comet directory.
Edit your comet.ini file in the comet folder as so:
[SITE]
...
Server = N00,TCP,L,192.168.1.200; win2003 server
...
[DIRECTORIES]
00 = c ,$(catemp);
01 = c ,\\win2003\comet\cos\;
02 = c ,\\win2003\comet\rel\;
03 = c ,\\win2003\comet\utl\;
...
[NODE]
Name = cfam; or whatever the client name you want
Server = N00,cs;
Run Comet with a shortcut as follows:
Target: c:\comet\comet.exe /c
Start in: c:\comet
Run sysgen and generate all of the .CFG files for the clients.
Copy the .CFG files to the Novell server's comet folder.
Now, setup a shortcut on each client that includes the following:
Target: \\Novell\comet\comet.exe /pn=cfam
Start in: \\Novell\comet
Note that it may be even better to make two shares on the Novell server, one for the executables and the other for the .CFG files.
That is it. I hope I did not make this seem too complicated. It really is not that hard to do.
When the shortcut loads comet.exe, it will get all of the executables and ddl files etc from the Novell. It copies all of these files to a temp folder on each client machine. Comet will then load the configuration file (xxxx.cfg) from the novell as well. From then on, comet will use a proprietary protocol to access files on the Win2003 server.
Good luck with this and if you need any further help, or if anyone else has anything to add or correct in this post, please answer here so we all can learn more.