Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 612
  • Last Modified:

Novell popup messages not reaching all users

We are in a Windows NT40/95 shop all running off of Novell 4.11   Each time I send a Novell pop-up message to my entire group many of the popups do not get sent.  The Send Message results window usually shows about 50% of the users with the standard blue "X" representing that the message wasn't sent.  It doesn't matter if the user is on a NT or 95 box and their receive broadcasting is definitly turned on.  The *only* common thing that *always* is the same is that the people that don't get their popups have a "higher" connection number.  In fact, if I click on the "connection number" title (so everyone is sorted by connection number) everyone with lower connection numbers shows getting the popups and at some point there is a "cutoff" (unknown, varies from day to day!) as to when people don't get the popups.  Today that "cutoff" number might be 350, tomorrow it might be 400...
I haven't found anything conclusively as to why this is happening and how to fix it.  I have even considered a third party product but haven't found anything yet that is fairly inexpensive.
0
mfilip
Asked:
mfilip
  • 13
  • 8
  • 3
  • +9
1 Solution
 
jstegallCommented:
What client are you using?
What patches are install on the server?
0
 
paulnicCommented:
couple tests you might try...

1.  can you send a message to an *individual* w/a high connection number that didn't receive the broadcast to the group?

2.  does group size affect things?  Suppose the one big group were split in two...would only half of EACH group get the message?

Peace^^Paul
0
 
mfilipAuthor Commented:
ok, so I don't have all the facts... we don't actually administer the servers so I don't know what "patches" are installed on the server.  We are running the 4.11a client on our NT boxes and the latest client on the 95 boxes.  If I show that 10 people didn't get sent the message within a group then if I try to send to them individually I still cannot. I hope this answers your questions adaquetly.  I'm upping the points because I think it's a little tough to try to troubleshoot this one.
0
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

 
jlove1Commented:
Have you checked the status of the SEND command in netware?
Try using the SEND command on the clients that aren't getting the messages. It's probably because the send command has the messages disabled.

0
 
mfilipAuthor Commented:
I am able to use either the GUI or "DOS" level send to send to a user who, as part of a group, showed they weren't receiving the message.  That is to say that if I send a broadcast message to 50 people, the first 25 people (sorted by connection number) will show getting the message the the last 25 (highest connection numbers) do not show getting them.  I can then independently send any of the 25 (that didn't get them as part of a group) a message and it shows getting the message.  This works by either using the GUI or "dos" send command.  
I am now starting to record how many people total are logged in at the time I send a message and out of that group how many received it and how many didn't.
0
 
saar2Commented:
Just a little checks - try to send a message for a user with high connection number.

If it does not work go to NWADMIN and check if this user has a preffered server, if it does not - change it and try again.

Saar

saar@bigfoot.com
UIN: 3233305
0
 
jlove1Commented:
Try running the following from a client machine that CAN't recieve the messages and see if this helps:
send /a=a

Try it and let me know the results.
0
 
mfilipAuthor Commented:
Saar2's response: the preferred server is alread set and it is done at the workstation the user happens to log into.
Jlove1's response: It made no difference.  Also, remember that whatever "fixes", I need this to work from the standard GUI environment (my workstation in fact).  
0
 
tbaffyCommented:
Is your network subnetted with a router?  Many broadcasts packets are blocked by routers in their default settings.

Tom
0
 
saar2Commented:
mfilip, I am not talking about the preffered server in the workstation configuration.

Check the user's one in NWADMIN.

Saar
0
 
zhanghlCommented:
Please make sure all the client use same Ethernet frame, such as 802.2 or 802.3.
0
 
mfilipAuthor Commented:
I'm not sure everyone here is reading *all* of my stuff.  These users are receiving popups from me in an inconsistant manner.  One day User "A" can receive my popup, the next he cannot.  The only determination I can make from this is that on the day user "A" did receive my popup his connection number to the network was "low".  Users, on a given day, with high connection numbers do not receive my popup messages.  So checking something that is definitly not being changed is an unlikely "fix". Again depending on the connection number assigned to users when they log in seems to be the common denominator here.  I would check these various settings mentioned if they were somehow dynamic in nature.
0
 
tbaffyCommented:
Do you have any SET commands in startup.ncf or autoexec.ncf that set broadcast parameters numbers of sockets or SAPS?

tbaffy
0
 
mfilipAuthor Commented:
I have no files on my local drives that end with .ncf, so I would assume the answer to your question is no.
0
 
paulnicCommented:
a few thoughts after looking over this conversation:  

It may not seem apparent, but the server is directly involved in handling popup messages.  If you want to solve this there's a good chance you'll have to find a way to communicate with the folks who run the server, and ask them some of the questions people have been presenting to you in their effort to help.  

For instance, the support pack level and licensing status of the server may need checking.  A missing "preferred server" in NWADMIN may semi-randomly affect the connection number that a user gets...even though the missing setting doesn't change.  The NCF files are in directories on the server, usually accessible only to server administrators.   At some point, you have to decide whether you are serious about getting to the bottom of the problem, which just might take you in the direction of the server!

Peace^^Paul
0
 
tbaffyCommented:
The STARTUP.NCF and AUTOEXEC.NCF are files that reside on your server.  It is much more likely that this problem is a server side configuration issue rather than the client side.  Consider that you have already stated that the problem is related to the connection number of the station.  Also consider that this connection number is determined on the server side.  Also consider that the file server will initiate the broadcast communication that you are sending. All in all I think you can pretty much forget the clients.  If they can receive one popup message then all other popups are pretty much the same to the client.

Tom
0
 
mfilipAuthor Commented:
I will attempt to find out more information from the last two questions from the people in charge of the server(s).  Unfortunately this will be a slow and tedious process so please bear with me while I communicate to them.  Aren't all ISD's slow?
0
 
tbaffyCommented:
mfilip,

Do you have any administrative access to your server at all?  If you can see the contents of the SYS:SYSTEM directory then you can probably find out most of what we need to know yourself.

The AUTOEXEC.NCF file is in the SYS:SYSTEM directory.  It is just a standard text file and can be viewed with any text editor such as notepad.  If you can get to it, then look for a line in this file that says:

LOAD REMOTE ?????????

where ???????? is the remote access password for RCONSOLE.  If you can get this then you can find (and change) any of the server side configuration parameters you need.

Tom
0
 
mfilipAuthor Commented:
We have very little rights to our server. Our ISD deptartment retains most of the rights and we're basically limited to adding objects, setting file directory rights, etc.  This must be why I am not able to browse for the directories you mentioned.
0
 
tbaffyCommented:
See what you can find out then post another comment here to let us know.  My email will be anxiously awaiting ;).

Tom
0
 
JezCommented:
Have tou tryed a dsrepair at the server console?
0
 
tbaffyCommented:
jmcclell,

He doesn't have access to the server console.  He is still trying to find out about server configuration settings from his Info Systems department.

Tom
0
 
mfilipAuthor Commented:
I'm afraid I cannot newer information. I am unable to run server console or browse the directories mentioned so I can't answer the questions properly.  The only thing I can add new is that one of our ISD folks "claims" that there is a known bug in Netware 4.1 in regard to this problem.  I couln't find anything on the Novell site to back his claim up though.  I can also report that this problem occurs for any other techies in my section that send out popups, so it doesn't appear to be machine specific.  I apologize for the lack of info but I can only give out what I am given rights to "see".
0
 
tbaffyCommented:
That is bunk!  I have sent broadcast messages to hundreds of users simultaneously.  The only thing I can think of is that your network admins are running a hacked 25 user Netware.  That is why the first 25 stations work OK but everybody else doesn't.  They figured out how to hack the license for more network connections, but don't know how to tell message handling services to use more.

Tom
0
 
mfilipAuthor Commented:
I can assure you that being a State agency that our ISD folks are on the up & up on the licenseing issue.  And JSTGALL, as previously mentioned we are running the most current client 4.11a and I don't have access to information on what server patches have been installed.
0
 
jrbuckCommented:
go Tom, Go!
0
 
mfilipAuthor Commented:
Yes, an individual who is on the big list that didn't get a message will get an individual message.  I can't "split" the list into two so I don't know what would happen if I did.  By the way, my initial comment about 25 users wasn't exact and isn't consistant.  If I send out a group popup and there are, say 45, people logged in, it may only be that 20 of them get it, the next time 17, and so on.  There appears to be no consistancy other than if their connection number is higher, at some point, everyone past a certain (daily dynamic) point doesn't get the popups.
0
 
saar2Commented:
What happens if you send message for many users which all of them have "high" connection number?

If you had access to the console, you could use Auditcon to audit all the messages sending - this way you could know if the server gets all the messages or just few of them (which mean it is someing worng with the client).

Saar
0
 
mfilipAuthor Commented:
I can send individual messages to any users that previously didn't receive a message due to their "high" connection number.
0
 
tbaffyCommented:
mfilip,

I can assure you that your problem is related to a server resource.  There is something in one of the Netware memory pools that has to be adjusted in order to accomodate the broadcasts.

Tom
0
 
rjhawkinCommented:
in addition to checking the novell TID base you might want to do a check on the novell list archive located at:

http://netlab1.usu.edu

Your problem might have come up for discussion, Both the list archive and the FAQ can be reached from that page.

0
 
mfilipAuthor Commented:
Thanks for the additional info.
0
 
leltonCommented:
I had a similar problem, some of my workstations could receive broadcast messages, some could not. I found the sollution. It seemed to stem from those workstations that had the MS client form MS networks loaded, and only those that had the MS client loaded after Client32, it seems that the MS client messes up the Client32 if its installed after Client32. The sollution, a quick reinstall of Client32 solved the problem in my network and the missed broadcast messages problem was corrected.

Les Elton
abc@globalserve.net
0
 
mfilipAuthor Commented:
In this case this would not pertain to us.  Every one of our 95 and NT workstations are built exactly the same (from standardized install procedure).  We always install the latest Novell client in each case.
0
 
maryann071598Commented:
Are you using broadcast from the server console or the send command from a workstation?

Did you try using the send command at the DOS prompt? The users have to have the preferred server entered in NWadmin for this to work. Does broadcast from the console have the same results?

At a DOS prompt we use - Send "your message" .cn=everyone.o=org.


0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 13
  • 8
  • 3
  • +9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now