Computer Hope
Software => Computer software => Topic started by: Barefoot_Tom on July 08, 2006, 12:59:30 PM
-
I'm familiar with AIM for Instant Messaging. It requires Internet access to function. I have several computers (running WIN98SE, and WIN2000) set up on a local network.
Does anyone know of a software program I can use to do Instant Messaging from one of these computers to another, without going through the Internet? Or is there any way built in to Windows that I could accomplish this?
Tom
-
Take a look at NetMeeting. It's available on all Windows computers, and it works without an Internet-based server. It's has the features of Instant Messaging and more. See http://www.microsoft.com/windows/netmeeting/
-
Results 1 - 10 of about 13,900,000 for Messaging on LAN. :D
http://www.google.com/search?q=Messaging+on+LAN&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official
-
Ah, Viper, you do me proud! ;D
<----------------
-
Take a look at NetMeeting. It's available on all Windows computers, and it works without an Internet-based server. It's has the features of Instant Messaging and more. See http://www.microsoft.com/windows/netmeeting/
Thanks, I'll do that. If i have problems, I'll shout.
Tom
-
If you want a super-delux industry standard client-server instant messaging system, that's free, investigate Jabber. I currently deploy the ejabberd Jabber server and the Psi Jabber client. The server can be tricky to set up, but I have ejabberd running on a Linux server, integrated with Active Directory on Windows SBS 2003 and Windows XP on all the workstations. Works a treat. Popup messaging, instant chat, conference rooms, etc.
-
Take a look at NetMeeting. It's available on all Windows computers, and it works without an Internet-based server. It's has the features of Instant Messaging and more. See http://www.microsoft.com/windows/netmeeting/
I found, and installed, NetMeeting on 2 of the computers that are connected. It looks like that program would do what I want, but I can't get it to work. I am unable to enter the name of the server in the Windows Address Book, since none of the connected computers act as a Server. They are merely connected as part of a network. As a result, no names are in the address book
How can I identify the computers in a way that will satisfy Windows Address Book; or how can I avoid using WAB in order to identify the computer I want to contact?
Tom
-
Might try this:
http://www.dailysofts.com/program/852/15702/Lanconference.html
Alan <>< :o
-
Might try this:
http://www.dailysofts.com/program/852/15702/Lanconference.html
Alan <>< :o
The description of the program looks promising. Unfortunately, I haven't been able to download it. I even googled it to find other sites. There were plenty, but none of them let me downlaod the program. Looks like the company may have gone belly-up, or been bought by Yahoo.
Tom
-
I found, and installed, NetMeeting on 2 of the computers that are connected. It looks like that program would do what I want, but I can't get it to work. I am unable to enter the name of the server in the Windows Address Book, since none of the connected computers act as a Server. They are merely connected as part of a network. As a result, no names are in the address book
How can I identify the computers in a way that will satisfy Windows Address Book; or how can I avoid using WAB in order to identify the computer I want to contact?
Tom
Windows Address Book hsd nothing to do with it. Where did you get that notion? Do this look familiar?
(http://i7.photobucket.com/albums/y256/farmpond/forums/NetMeeting.jpg)
-
[/quote]Windows Address Book hsd nothing to do with it. Where did you get that notion? Do this look familiar?
(http://i7.photobucket.com/albums/y256/farmpond/forums/NetMeeting.jpg)
[/quote]
It sure do- And that is exactly as far as I can get. The difference between the screen you how, and the one I get is that mine shows "Not in a call" at the bottom. My problem at this point is how do I start a call? How do I identify the computer I want to reach?. There are only 2 computers connected.
And as to where I got the idea about the ddress Book, it seemed a logical way to put the name of a computer into play.
Tom
-
Tom,
If you shoot me your email address I'll send you a zipped file with the Lanconference program (it's only 827kb) .
Mine is: [email protected]
Alan <>< ;D
-
I have a Win XP computer networked with a Win 98SE computer, via a D-Link DI-524 router. To "call" from XP to 98SE, I enter 192.168.0.101 in the To: box of the Place A Call panel. To call from the 98SE comp to XP, I enter 192.168.0.100 in the To: box of the Place A Call panel.
If you were using NetMeeting over the Internet, you would enter the IP address of the remote computer.
-
I have a Win XP computer networked with a Win 98SE computer, via a D-Link DI-524 router. To "call" from XP to 98SE, I enter 192.168.0.101 in the To: box of the Place A Call panel. To call from the 98SE comp to XP, I enter 192.168.0.100 in the To: box of the Place A Call panel.
That sounds reasonable. I tried it, and it doesn't seem to work. I can'treally tell at the moment, though, because the computer I'm calling has no one at it, and I'm running back and forth between them. There doesn't seem to be any indication at the computer being called that anyone is tring to contact them.
I'll know more later.
Tom
-
From a Command Prompt type ipconfig /all and hit Enter...this should report each machine's address on the network.
patio. 8-)
-
Yes, do what Patio said. At the receiving computer, you should the sound of a phone ringing and a panel will pop up asking whether to Accept or Ignore.
-
From a Command Prompt type ipconfig /all and hit Enter...this should report each machine's address on the network.
patio. 8-)
It does. That wasn't my problem though ( I'm beginning to think the real problem is terminal stupidity). I have the IP addresses of the computers. I'm just not able at the moment to check both of them simultaneously.
Tom
-
Yes, do what Patio said. At the receiving computer, you should the sound of a phone ringing and a panel will pop up asking whether to Accept or Ignore.
At least temporarily I've cured my terminal stupidity. I set up another computer on the network,; this one within sight of my main computer. Using the IP address to call, I was able to both talk, and "Chat" back and forth.
It appears, however that, in contradistinction to AIM, one must have Network Meeting Up and running (or at least minimized in the toolbar in order for it to function. Is this so; or can one put it into the SysTray?
Tom
-
If you go to Tools, Options, General, and check the box for "Run NetMeeting in the background when Windows starts.", NetMeeting will respond to a call without having to start it from the Programs menu. You also have an option to "Show the NetMeeting icon on the taskbar."
-
If you go to Tools, Options, General, and check the box for "Run NetMeeting in the background when Windows starts.", NetMeeting will respond to a call without having to start it from the Programs menu. ."
Thanks,
Those suggestions should take care of things nicely.
Tom
-
If you go to Tools, Options, General, and check the box for "Run NetMeeting in the background when Windows starts.", NetMeeting will respond to a call without having to start it from the Programs menu. You also have an option to "Show the NetMeeting icon on the taskbar."
For anyone interested: this option is not available under WIN98SE. It is available for those using WIN2000. The file "CONF.EXE" is a different version in each. For anyone who wants it, I will send them the WIN2000 version, although you could probably get it from Microsoft as well.
Tom
-
Tom, you may be quite right about that. And, the solution, as you said, is to upgrade NetMeeting in Win 98SE from the verion that originally came with it to verion 3.01. I did that, so my Win 98SE machine allows the same setting as Win XP.
Here's the download source for NetMeeting 3.01: http://www.microsoft.com/windows/netmeeting/download/default.asp
-
Here's the download source for NetMeeting 3.01: http://www.microsoft.com/windows/netmeeting/download/default.asp
FWIW, the version with WIN2000 is 4.4.0.3385
Tom
-
If it works with Win 98SE, then OK. Have you tried it? The Microsoft page I cited says:
Windows NetMeeting 3.01:
Windows NetMeeting for Windows 95, Windows 98, Windows Me, and Windows NT 4.0.
I find it odd that the version in Win XP is 3.01. Actually, it must be a little different than the version in the above reference. In Win XP, NetMeeting Help shows version 3.01 (5.1.2600.2180). In Win 98SE: version 3.01 (4.4.3388). Makes me wonder what number you're talking about, the number in parentheses or a number before the parentheses.
-
In Win 98SE: version 3.01 (4.4.3388). Makes me wonder what number you're talking about, the number in parentheses or a number before the parentheses.
There are no parenthese. I'm talking about the version of the file CONF.exe which is in the NetMeeting Folder. The number above is displayed when you click on the Properties tab for that file.
Tom
-
The version number you see on the Properties tab for that file is the number that appears in parentheses in on the NetMeeting Help screen. So, the version I have in Win 98SE, which I downloaded from the web page previously posted, is a little more recent than the version you have in Win 2K.