| New mail notification tends to be one of the touchiest
areas to set up. I'm afraid we don't have a lot of
information on troubleshooting. If you have TeamLinks
for Macintosh, there is a fairly extensive discussion
on the topic in the Troubleshooting guide, which is installed
in the TeamLinks Office folder.
In this case, I would start by testing the connection
from the server back to the clients. Log into the server
and from a terminal session, enter:
telnet full.node.name.of.pc 2020
<then type a string>
<hit return>
You should get the message "connection closed by foreign host",
but you should also get the string you typed to appear in the
notification window of the client PC.
If not, you need to look at the network (e.g. routers) between
the server and the remote clients.
Also, make sure that the name service (DNS) has entries for
all of the PCs, including the reverse mappings from the
numeric form back to alpha form. This reverse mapping is
recorded in an IN-ADDR.ARPA entry in the DNS database - again,
this is described in more detail in the Mac troubleshooting
guide (under "using TCP") - if you need more information, let
me know.
-Stan
|
| > I believe that TeamLinks for Windows also has on-line
> documentation regarding new mail notification.
There's *some* online documentation in the TeamLinks for Windows
Client Administration Guide (which is now in Windows help format),
but not a lot about working with MailWorks for UNIX specifically.
The online help for TeamLinks Information Manager has a topic with
info for MailWorks for UNIX users. All it currently says about new
mail notification is:
>To keep new mail notification working correctly, you should turn on the
>Enable on each connection to mail service checkbox in the New Mail
>Notification dialog box in Information Manager. This is necessary because
>the MailWorks for UNIX >server does not store the new mail notification
>setting.
FWIW....
-- Nina (TeamLinks doc'n)
|