![]() The initial communication and session setup is conducted through Windows Messenger via server mediation. To begin with, video conferencing and voice conversation require both server-mediated and peer-to-peer sessions. They’re also the most troublesome when it comes to working with a firewall and NAT. Video conferencing and voice conversation are probably the most exciting features that Windows Messenger has to offer. Video conferencing and voice conversation Packets returning from the IM server are likewise in proper order and allowed to pass through the firewall. Then, when the packet hits the firewall, both the destination and source credentials (IP addresses and port numbers) appear to be in proper order, and the firewall allows the packet to pass. When the packet hits the NAT, the private IP address is replaced by the public IP address. The client’s private IP address is also added to the packet along with the port number. Let’s take a closer look at this last point, because the success of IM will help you understand the failure of some of the other Windows Messenger components’ communication operations.Īs a packet to be sent from an IM client to the server is created, the IM server’s IP address and the correct port number are added to the packet. Furthermore, the packets that make up the underlying IM communication contain the proper credentials. In fact, IM text is packaged as hypertext and uses the Hypertext Transfer Protocol (HTTP). Since the IM messages are text-based and use the TCP connection, they can sail right through your firewall just like the information that makes up the pages that your browser renders. Since the communications are server-mediated sessions, messages between the two parties are actually sent to the server, which then forwards them to the recipient-there’s no direct connection between the two parties.It can ride along on the TCP connection without any special considerations. The information transferred in IM sessions is text-based.IM and Presence don’t have any real problems working through a firewall or NAT because both IM and Presence can use the TCP connection and are actually server-mediated sessions. Presence is a component of IM that allows you to see when your friends are online. Of course, IM provides users the ability to send and receive typewritten messages in real time. Probably the biggest uses for Windows Messenger are instant messaging (IM) and Presence. Let’s take a look at each one of Windows Messenger’s components and focus on the types of problems that can arise when you try to employ these components behind a firewall and NAT. ![]() I’ll then explain how all these pieces must function together in order for all of Windows Messenger’s components to work. I’ll start at the bottom and work up as I examine each piece in the puzzle. I’ll explore the ins and outs of how Windows Messenger works with a firewall and NAT component. You’ll need to be prepared to perform some additional configuration to get all of Windows Messenger’s components to work properly, and to do so, you really need to have an understanding of the underlying technology. ![]() The chances of you falling into the former are pretty slim. In other cases, certain components will be limited or not work at all. In some cases, all of Windows Messenger’s components will work just fine with your firewall and NAT. If you’re thinking about employing Windows Messenger as a communication tool on your network, you need to be aware of how it will interact with your network’s first line of defense-the firewall-as well as Network Address Translation (NAT) components. These types of real-time electronic communication stand ready to revolutionize the way that your company does business. Additional features, such as making calls to a regular phone and sending instant messages to pagers are also possible with Windows Messenger. Windows Messenger opens the doors to all kinds of real-time electronic communication: instant messaging, video conferencing, voice conversation, remote assistance, and application sharing and file transfer. Greg Shultz explains why firewalls and NAT cause connection problems and shows you ways UPnP can help. But it's a challenge when firewalls and NAT are involved. Windows Messenger can connect your users in exciting new ways. Get Windows Messenger to work with firewalls and NAT
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |