Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Utility: LANegram - NET SEND Replacement 2

Status
Not open for further replies.

1DMF

Programmer
Jan 18, 2005
8,795
GB
Hi,

I've been using this utility for quite a while now and in general it works great apart from one small niggle.

If someone is typing and they receive a message, their typing dismisses the message before they get to see it.

It seem pressing any key is the same as clicking the OK button, any idea how i can make them have to click the OK beofre the message vanishes?

Cheers,
1DMF

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

Google Rank Extractor -> Perl beta with FusionCharts
 
Somebody reported a ridiculous bug I had missed. It only impacts those using the "standard" interface and not the "simple" one though.

Once 100 messages have arrived, new messages were supposed to push the oldest off the list. This wasn't working right and it looks like the 100th just got replace by the 101st, and then the 101st (being now 100th) was replaced by the 102nd, and so on.

The order of messages has changed, I hope this doesn't cause anyone grief. Now the newest is listed at the top, previous below it, and so on with the oldest at the bottom.

This version can run in a mixed network where some machines have an older version.


The "upgrade" install is still problematic: please uninstall any older version before installing this new one (version 3.3). This is still on the to-do list here but it turned out to be messier than anticipated.

You can use the same link as above to get this new version (MSI and source), or use this one: LANegram 3.3
 
I can't seem to get it to work anymore since the last update, some get the message some don't?

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

MIME::Lite TLS Email Encryption - Perl v0.02 beta
 
Hmm, that seems odd. The actual changes were very minor and not to the part that handles communication at all. I just did a WinDiff to make sure, too.

I'll look some more. Is there anything else that has changed there that might isolate some machines? Any funky network changes like new routers?
 
Yes we have had a new router put in and I did change our IP range/sub net mask, but still when I do a global '*' messsage only some get it. They also don't get the message if I send it direct to their machine?

I've uninstalled, reinstalled several times, but no joy?

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

MIME::Lite TLS Email Encryption - Perl v0.02 beta
 
Without "help" from the router the Mailslot Broadcasts LANegram (and the old Messenger Service) use, messages can only be sent within the subnet or LAN segment. Sometimes switches can block this traffic too.

At the next level lower these are normally UDP broadcasts today (assuming you are using TCP/IP to carry MS Networking traffic, a very good bet). Many routers are MS Networking-aware though and can be configurared to relay this traffic between subnets.

UDP ports 137 and 138 are usually the ones to be concerned with. TCP 139 is used by Mailslots but only for non-broadcasts which LANegram doesn't do anyway.


So yes this new router could be the problem, either by itself or due to subnet separation. It may be possible to fix this with a router config option though. People often do this to avoid the need to run WINS servers too, so it isn't a rare and exotic option.
 
We are all on the same new ip ranges? Some get it and some don't.

I might at some point uninstall it off all users machines and go back to the original version and see what happens.

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

MIME::Lite TLS Email Encryption - Perl v0.02 beta
 
Worth a shot I guess. But as I said I can't find a single line of code that changed outside of the part handling displayed messages in the standard user interface window.

Perhaps others will say something before long. I'm not sure what else to look at though.
 
yup, mystery to me too, it was working fine on all machine, but ever since I upgraded to the latest version it hasn't worked properly since.



"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

MIME::Lite TLS Email Encryption - Perl v0.02 beta
 
Maybe replace the new with an older version, see if anything changes? Probably only have to test one machine, the messaging is unchanged so they should be compatible.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top