|
-
Jul 25th, 2006, 06:30 AM
#1
Thread Starter
Just Married
-
Jul 25th, 2006, 02:28 PM
#2
The most difficult part of developing a program is understanding the problem.
The second most difficult part is deciding how you're going to solve the problem.
Actually writing the program (translating your solution into some computer language) is the easiest part.
Please indent your code and use [HIGHLIGHT="VB"] [/HIGHLIGHT] tags around it to make it easier to read.
Please Help Us To Save Ana
-
Jul 26th, 2006, 12:16 AM
#3
Thread Starter
Just Married
-
Jul 26th, 2006, 01:34 PM
#4
Re: Concept Of Lan Chat
 Originally Posted by shakti5385
And type a message then the message goes to another pc….
You described the program named Netsend.
The most difficult part of developing a program is understanding the problem.
The second most difficult part is deciding how you're going to solve the problem.
Actually writing the program (translating your solution into some computer language) is the easiest part.
Please indent your code and use [HIGHLIGHT="VB"] [/HIGHLIGHT] tags around it to make it easier to read.
Please Help Us To Save Ana
-
Jul 27th, 2006, 02:00 AM
#5
Thread Starter
Just Married
Re: Concept Of Lan Chat
You described the program named Netsend.
so what happen?
-
Jul 28th, 2006, 09:18 PM
#6
Re: Concept Of Lan Chat
I was just saying that what you want to write was written decades ago. If you search for Netsend source you'll probably find hundreds of hits.
The most difficult part of developing a program is understanding the problem.
The second most difficult part is deciding how you're going to solve the problem.
Actually writing the program (translating your solution into some computer language) is the easiest part.
Please indent your code and use [HIGHLIGHT="VB"] [/HIGHLIGHT] tags around it to make it easier to read.
Please Help Us To Save Ana
-
Jul 29th, 2006, 03:27 AM
#7
Thread Starter
Just Married
Re: Concept Of Lan Chat
If U R Able To Send Me The Link Then It Is Very Best Idea
-
Jul 29th, 2006, 04:54 PM
#8
The most difficult part of developing a program is understanding the problem.
The second most difficult part is deciding how you're going to solve the problem.
Actually writing the program (translating your solution into some computer language) is the easiest part.
Please indent your code and use [HIGHLIGHT="VB"] [/HIGHLIGHT] tags around it to make it easier to read.
Please Help Us To Save Ana
-
Jul 29th, 2006, 09:42 PM
#9
PowerPoster
Re: Concept Of Lan Chat
if it uses the Messenger Service,
Messenger Service is disabled in XP SP2 by default as is a security risk ..
-
Jul 31st, 2006, 12:19 AM
#10
Thread Starter
Just Married
-
Jul 31st, 2006, 12:26 AM
#11
Thread Starter
Just Married
Re: Concept Of Lan Chat
this very help full.... again i am testing..........
please some wait...
thanks
-
Aug 1st, 2006, 09:39 AM
#12
Re: Concept Of Lan Chat
While there is a known buffer overrun vulnerability in the Windows Messenger Service in NT operating systems (NT 4.0, 2000, XP, 2003) there is a patch for it too. Microsoft Security Bulletin MS03-043.
These are just an inevitability when you use software written in unsafe languages like C. The only cure is lots of eyeballs going over the code for bugs like this, one answer perhaps being to use OpenBSD where the code is heavily scrutinized.
All that said, there is nothing inherently unsafe in the communications infrastructure used by NET SEND and the Messenger Service (or WinPopup on Win9x systems). Windows Networking Mailslots are a really nice little UDP-like communication technology.
As long as you have NetBIOS connectivity between systems and they are in the same Workgroup or Domain Mailslots work nicely for LAN messaging. One advantage is that you don't need to tie up a TCP port number, the traffic is multiplexed over the channels used for File and Print Sharing services. Another is that Mailslots programs work transparently over TCP/IP, IPX, or even NetBEUI. Yet another is the vast namespace available with Mailslots, unlike the 64K of port numbers used for TCP/IP.
Mailslots also present some small obstacles. Nothing is perfect.
One thing is that only one instance of a given Mailslot can exist on a machine - but that's a lot like saying only one program can Bind to a given TCP or UDP port. Another is that in when machines allow NetBIOS over multiple protocols (TCP/IP and IPX for example) a message sent to a Mailslot will get there once for each protocol in use. The datagram limit is also 424 bytes for Mailslot broadcasts.
The big thing is that there isn't any standard ActiveX component for doing Mailslots. Instead you have to code to the API. See About Mailslots for details.
-
Aug 1st, 2006, 02:25 PM
#13
PowerPoster
-
Aug 1st, 2006, 03:00 PM
#14
Fanatic Member
Re: Concept Of Lan Chat
I'm sorry, but I can barley understand what you are trying to do...
But my best bet would to send a message to the broadcast address on your network asking who is out there, and the client program (that you write) would respond "I'm here!" (ok not exactly that...maybe a certain byte if the user is at the computer, 0x01, logged out, 0x02...ect).
And creating it from there is a basic relay server, (unless you want usernames/passwords, even then it wouldn't be that hard).
-
Aug 2nd, 2006, 12:24 AM
#15
Thread Starter
Just Married
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|