To the best of my knowledge, I have Bat 1.41 set up properly in Server mode
on Machine1 and Bat 1.39 set up properly in Client mode on Machine2. When
I tell Bat-Machine2 to check its mail (Account2), I see the ethernet lights
blink in a pattern that seems to reflect valid communication between the
Bats. Yet, Bat-Machine1 does not dial out. If I tell Bat-Machine1 to
check its mail, Machine1 dials out successfully.
The instructions on how to set this up has lost some clarity in the
translation but I believe, with some modofications, I have set it up
correctly.
Bat-Machine1 (Account1):
Program files on drive E: - not shared
Message base directory on drive F:(shared)\Account1
TCP/IP or Dialout Server
Bat-Machine2 (Account2):
Program files on C:
Message base directory on \\Machine1\F\Account2
Non-TCP/IP Workstation
I needed to use UNC notation because, as I interpret the instructions, I
need to put all or part of Bat-Machine2 on drive "F:" which has been mapped
to Machine1\F:. But Machine2 already has a drive F:. So, in my earlier
experiments, I mapped Machine1/F: to Machine2 local Y: but that didn't work
either. The registry elements have been modified to reflect the message
base path.
The question is, should the Bat-Machine1 executables have been installed in
a sharable drive? By what method are the commands issued by Bat-Machine2
sent to Bat-Machine1? On what channel is Bat-Machine1 listening for
commands from the clients?
Brian Smither
[EMAIL PROTECTED]
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
