Message Service Weirdness

  • Thread starter Thread starter Bart
  • Start date Start date
B

Bart

Okay, get ready for this one.
I do IT for a small business in NY(~40 users). About 3
months ago I set up a fax server that lets users get faxes
through Outlook. Before the fax actually arrives, the user
gets a popup from the Messenger Service on the fax server
telling them that they are about to receive a fax.
2 days ago a user ('User A' for the sake of the story)
came to me and told me that he was getting fax-
notification popups for another user('User B'). User A was
not getting User B's faxes, just the notification popup.
The story took a strange turn when I looked at User A's
workstation. Using Net Name I discovered that User B was
not recognized on User A's workstation. Further, when I
sent a message to User B using Net Send it appeared on
User A's machine, but not on User B's! User B accesses our
network through a Terminal Services session, and so I had
our TS Administrator use Net Name on the Terminal Server
to find out if User B was recognized. When he tried to
invoke Net Name he discovered that the Messenger Service
on the Terminal Server had not been started, and when he
tried to start it the service wouldn't start.
Now: even if User B could not receive his messages
because the Messenger service was disabled, why would User
A - who uses a local machine and accesses shared resources
on the network - get User B's messages?
Some more background information: User A's workstation
is running Windows 2000, User B accesses TS from a Windows
2000 machine, our Terminal Server is running Server 2003,
Fax Server is running Server 2000.
Well, I am officially baffled. Anything you guys can
tell me would be immensely helpful.
 
are you using the nwclient32 or did i miss something remotely novell related
in your post?
 
Back
Top