Free ipx software for windows

WinSent Messenger 2.0 beta 3 brings you an easy to use software designed for instant messaging within local area network. Allows to send and receive messages using computer network name, user login, and nickname. Sends broadcast messages using workgroup or domain name. WinSent is fully compatible with WinPopup and Windows NT Messenger Service (net send). Works with any versions of Windows. Does not require dedicated server.

Major Features:

1. WinSent Messenger is a free instant messenger for LAN
   • WinSent Messenger is an easy-to-use program, intended for instant messaging and communication within local area networks (instant messenger for LAN). It can be used for communication between users of your home, enterprise or office LAN.
     
   • With WinSent's help you will be able to exchange short text messages with any user in your LAN, who have WinSent or compatible program installed.
   • WinSent Messenger allows to send and receive messages using computer network name, user login, nickname (arbitrary name, that is unique on the local network). Sends broadcast messages within the bounds of the network using workgroup or domain name. WinSent is capable of sending a message at once to several recipients.
2. Full compatibility with WinPopup and messenger service (net send) protocol
   • For message transmission the WinSent Messenger uses full implementation of a protocol, that is used for message exchange by software products like Microsoft WinPopup, Windows NT Messenger Service (net send command), etc. Therefore the WinSent is fully compatible with these products.
     
   • This feature enables to send and receive messages from network computers, that have one of the aforementioned programs installed and allows to use the WinSent as full replacement for Messenger Service (net send command) and Microsoft WinPopup.
     
   • You will be able to receive messages that are sent by system administrator with the "net send" command, with the Microsoft Winpopup utility, messages from Unix users, that are sent with the smbclient command, messages from printer spoolers, etc.
   • Full WinPopup protocol implementation allows to perform message exchange using both computer network name and user name.
     
3. Does not require a dedicated server or an internet connection
   • WinSent Messenger sends and receives messages in real time, without using intermediate servers. The messages are transmitted directly between sender and recepient. WinSent does not require a dedicated server, third-party services or an Internet connection.
   • As WinSent is not using insecure public networks (Internet), your secrets are safe. Messages are transmitting within your local network only.
4. Works over any network protocol in any versions of Windows
   • WinSent Messenger works over virtually all network protocols (TCP/IP, IPX/SPX, NetBEUI, etc.), in all Windows versions (95/98/ME/NT/2000/XP/Vista), including Windows Vista, where Messenger Service and net send command are missing.
5. Easy to use and handy interface
   • WinSent Messenger have simple and handy user interface without excesses. It looks and works almost like the ordinary Microsoft WinPopup, but have considerable improvements. WinSent does not clutters up the task bar. Its icon is placed in the system tray near the clock. As soon as you have received a new message, WinSent informs you by flashing tray icon.
   • You can configure what WinSent have to do when a new message arrives, including sound effects. WinSent supports configurable hot keys and have embedded local network browser. Most of WinSent's windows have configurable size and screen position, and these settings are stored.
6. Low usage of system resources
   • Low usage of system resources comes out of the great optimization work. WinSent Messenger is a compact program.
     
   • It requires about 300 KB of hard disk space. WinSent works silently in background mode, consuming very small processor resources.
7. Freeware
   • WinSent Messenger is absolutely free program. To be convinced of all aforesaid just download and install the WinSent. Taking into account the small size of the program you'll not spend a lot of time for it.

Enhancements:

• Include unspecified updates, enhancements, or bug fixes.

GIT is a utility to link two or more LANs together for network gameplay by tunneling packets over the internet via UDP, TCP, or even through a socks proxy.
It is very configurable, allowing only certain frame types, IPX packet types,
IPv4 protocols, IPX socket destinations, or TCP/UDP ports to be forwarded.
Unlike many other tunnel programs that send all packets over the internet, GIT is very friendly to low-bandwidth users, by not forwarding NetBIOS or other unneeded sockets by default.
It can also be used to bridge many configurations of IPX or IPv4 packets and frames from once point to another. Formerlly known as the Gamers IPX tunnel, GIT now tunnels TCP and UDP ports as well, in order to work with modern games.
New in GIT v0.99 is the configuration wizard, which allows you to answer a few questions to easily set up GIT for a particular program.
.git files can be run and will start GIT or talk to an existing GIT to display
the wizard pages needed for that script.
Please note that the Auto Configure button for the scripts will re-use all of
the saved settings from the last time you ran that script, so if your IP address
or any remote IP addresses have changed, you will need to run through the wizard again instead of using the Auto Configure button.
See the file "Wizard Scripts.txt" for information on creating your own scripts.
There is also a Save Profile option that will save all your current settings to
a wizard script that you can easily restore using the wizard later.
The host list can be stored as-in or the profile can create a textbox that will prompt to edit the host list when you run the profile script.
GIT puts your ethernet adaptor into promiscuous mode in order to sniff all
ethernet packets and analyze which ones are part of your network game traffic.
GIT then sends these packets to another instance of GIT running on the
opposite LAN, which will receive the packet and broadcast it onto that LAN
as if the two were physically connected.
Only one computer in each LAN needs to be running GIT for the entire LANs to be linked together.

System requirements:
- WinPcap 4.1 Beta 4

Enhancements:
- Dont Send Unicast - This replaces the old option named "Only if broadcast" but is only enforced on the sending side of the tunnel. Previously the option could reject packets on the receiving end of the GIT tunnel as well, but this is no longer the case.
- Dont Send Broadcast - This option compliments the previous option, and when combined with the previous option replaces the old option named "Receive only". This option is useful on a switched network with 2 or more copies of GIT running where GIT is forwarding unicast packets. Check this option on all but 1 copy of GIT in order to prevent duplicate forwarding of broadcast packets from the same network.
- Dont Send Routable - This option prevents any packets that should be routable over the internet from being tunneled. The only non-routable addresses that will still be tunneled are 192.168.x.x, 172.16-31.x.x, 10.x.x.x, and 169.254.x.x
- Also Match Source Port - This option allows the TCP/UDP port lists to forward packets if the source port matches a port in the list. Previously only the destination ports were matched, as is still the case for IPX sockets. This option should be checked on both sides of the tunnel if used.
- Forward ARP - This allows GIT to tunnel ARP requests and replies, in case some program requires it.
- Use Old Reforward Prevention Method for IPX/IPv4 Frames - Checking this option will resort to the method used up to GIT v0.97, which is to alter packets with a flag in order to not reforward them. Not checking this option will keep track of the source MAC addresses of all packets received from the tunnel and sent to the local network. Each MAC address is remembered for 30 seconds in order to prevent re-forwarding the same packet back that GIT had just created. Up to 256 MAC addresses can be remembered at once, otherwise packets may start getting duplicated once the table fills up. This should be unlikely though since it requires more than 256 unique computers to all have their packets tunneled at once in less then 30 seconds. ARP packets always use the MAC address method regardless of this setting.