Discussion Locked

NW3.12 Clients Get Annoying Broadcasts

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Netware 3.12 Users Get Annoying Screen
Notification of Incoming Email and Network
Broadcasts

We have an ancient NW3.12 network (going to
4.11 soon) which uses the current Novell 3.21
client. Many of our stations, on receiving a
network broadcast or even a simple email
message, interrupt Windows operations with
either a typical Windows 9.x inset window or
a large, annoying, DOS-like black-type-on-red
screen inset on a full-screen black window
(clearly a DOS video mode). We would like to
turn all such displays off permanently.

For example, if I send a test message to Ms.
Smith, the message may arrive on her screen
as a large, old-fashioned black DOS
characters in a red banner-type inset screen
"Netware Broadcast Message from [party name
here] CTL-ENTER to Clear" which completely
clears the Windows desktop view for a DOS
window) (alternatively, as a small,
blue-edged inset on the Windows desktop with
essentially the same title and information.
Checking the settings on the client
properties/ advanced settings, I cannot
disable "send message" without disabling
entirely the ability to send messages over
the network. When I disable the function,
the user is advised "You cannot send
messages. See system administrator."

I have experimented with Broadcast mode,
setting it from "ALL" to "Server only" and
then to "None", but even when the workstation
client's "advanced settings" no longer shows
a "Broadcast mode"+ option, the messages
continue to appear as obtrusively as ever.

Should the client settings to a bindery
Netware 3.x server be "bind + NDS" or merely
"bind"? I am aware 3.x is only bindery,
but we coexist with NDS servers on this
campus network. Would this setting have
anything at all to do with obstrusive screen
messaging?

This problem with the large, DOS-like red
message screen inset is erratic-- it comes

9 replies

by bock2000

I have not found a definite way to turn off this feature. The reason the DOS version is eratic is that it will display is you are working in a dos program.

One thing you can try is under Netware Client Properties / Advanced setting/ Message Timeout. This can be set to something other than zero. We have had mixed results with this option. Users still can be disrupted because it sometimes makes your current window inactive.

Hope this helps!

by alphaa10

Good answer, but we have tried all but Message Timeout reset to non-zero.
But as Bruce indicated, users can still be disrupted when their current window
may become inactive.

They are upset with me, alreaddy.

by alphaa10

Jim,
We tried castoff on an experimental basis with a station or two, but the
problem with that is it disables ALL incoming messages, doesn't it?

We occasionally need to announce the network is going down for
maintenance, or similar announcement. Castoff would neuter that option
for us.

by rogerndgreen

I agree with Answer #2 - Give him the points.

As for the fact that some clients have a popup window & others are providing full-screen DOS messages, check that you only have one nwpopup.exe on the DOS-like workstations. If you have try re-installing the NWclient - something has cashed with the popup functionality.
The Broadcast function is what it says (broadcasts from the workstation).
As for the client settings of BIND or BIND + NDS this will be your shout.

If you were running pure bindery LAN it would have no effect.
If Pure NDS, then NDS would be required (obviously). In a mixed environment, I would suggest that you use both (especially as you are planning a migration to all NDS soon) as it saves you having to reconfigure workstations during rollout.
As far as I recall, the order you specify is important i.e. if the NET.CFG says BIND, NDS, then the workstation will try to make a bindery connection first, NDS second and vice versa.
You may want to consider the implications of these users logging into the NDS tree and then use Netsync to map the NW3 resources into NDS objects?

Hope this helps

Roger

by alphaa10

Roger,
This is getting close to where we are on the problem, except for
reinstalling the client (already done). The DOS-like windows do not
appear to manifest in a double or triple nwpopup load for the station.

by jimbb

Castoff does not disable all messages, you'll still get the "volume sys almost out of disk space" kind of messages. Castoff /all will block everything. Typically you'll use that for a dedicated machine (like some fax servers) where you have applications that stop responding until someone presses Ctrl+Enter to clear the message.

Jim

by estebandelatorre

Place a line like this into your login script file for every client

f:\public\castoff.exe

This will disable all messages to be popped up

This discussion is closed to new replies.