微软大拿们
- 主题发起人 oread
- 开始时间
To connect from behind a firewall
Sign in to Windows Messenger.
You should automatically connect to instant messaging services―even from behind a firewall.
Windows Messenger will first attempt to connect directly so that you can use its full functionality. If Windows Messenger cannot connect directly, it will use the same HTTP connection that your default browser uses to connect to the Internet.
Important: If Windows Messenger uses your browser connection, you'll be able to send instant messages, but some features of Windows Messenger―such as placing calls, sending files, or connecting to other messaging services―may not be available.
Notes
To find out what kind of connection you have, go to the Connection tab of the Options dialog box (Tools, Options). In the bottom half, you'll see the type of connection you have―for example, "You are currently connected to Windows Messenger using your default browser's settings."
To get full functionality and avoid using your default browser connection, ask your system administrator to refer to the Guide for Network Administrators and the topic Configure your network for voice and video communications, application sharing, Whiteboard, and Remote Assistance.
Sign in to Windows Messenger.
You should automatically connect to instant messaging services―even from behind a firewall.
Windows Messenger will first attempt to connect directly so that you can use its full functionality. If Windows Messenger cannot connect directly, it will use the same HTTP connection that your default browser uses to connect to the Internet.
Important: If Windows Messenger uses your browser connection, you'll be able to send instant messages, but some features of Windows Messenger―such as placing calls, sending files, or connecting to other messaging services―may not be available.
Notes
To find out what kind of connection you have, go to the Connection tab of the Options dialog box (Tools, Options). In the bottom half, you'll see the type of connection you have―for example, "You are currently connected to Windows Messenger using your default browser's settings."
To get full functionality and avoid using your default browser connection, ask your system administrator to refer to the Guide for Network Administrators and the topic Configure your network for voice and video communications, application sharing, Whiteboard, and Remote Assistance.
To configure your network for instant messaging and file transfer
Note: This is part of the Guide for Network Administrators. It is not intended for end users.
As a network administrator, you can improve the way the people on your local area network connect to instant messaging services. Windows Messenger will connect users on a local area network to instant messaging services by using the same connection that their default browser uses―if it can find no other way. Connecting like this limits the functionality of Windows Messenger mainly to sending instant messages and seeing who is online.
For your network users to enjoy the best performance and full functionality―including transferring files―you may be able to configure your proxy servers in a way that enables them to connect directly to the instant messaging servers.
For instant messaging
To allow your network users to have a direct connection to instant messaging services, you will need to:
Open outgoing TCP connections to Port 1863 on your proxy servers.
Let your network users know which kind of proxy server your network uses (HTTP, SOCKS4, or SOCKS5) and provide them with the corresponding details (server name, port number, and so forth) so they can enter that information on the Connection tab of the Options dialog box (Tools, Options).
Make sure the internal local area network has access to the Domain Name System (DNS) servers to resolve the names of external hosts such as messenger.msn.com.
For file transfer
Both incoming and outgoing TCP connections use this range of ports: 6891 to 6900. This allows up to 10 simultaneous file transfers per sender. If you open only Port 6891, users will be able to do only one file transfer at a time.
The TCP ports need to be configured so that sockets on a port remain open for extended periods of time.
Note
File transfer may not work if you are behind a network address translation (NAT) device.
Note: This is part of the Guide for Network Administrators. It is not intended for end users.
As a network administrator, you can improve the way the people on your local area network connect to instant messaging services. Windows Messenger will connect users on a local area network to instant messaging services by using the same connection that their default browser uses―if it can find no other way. Connecting like this limits the functionality of Windows Messenger mainly to sending instant messages and seeing who is online.
For your network users to enjoy the best performance and full functionality―including transferring files―you may be able to configure your proxy servers in a way that enables them to connect directly to the instant messaging servers.
For instant messaging
To allow your network users to have a direct connection to instant messaging services, you will need to:
Open outgoing TCP connections to Port 1863 on your proxy servers.
Let your network users know which kind of proxy server your network uses (HTTP, SOCKS4, or SOCKS5) and provide them with the corresponding details (server name, port number, and so forth) so they can enter that information on the Connection tab of the Options dialog box (Tools, Options).
Make sure the internal local area network has access to the Domain Name System (DNS) servers to resolve the names of external hosts such as messenger.msn.com.
For file transfer
Both incoming and outgoing TCP connections use this range of ports: 6891 to 6900. This allows up to 10 simultaneous file transfers per sender. If you open only Port 6891, users will be able to do only one file transfer at a time.
The TCP ports need to be configured so that sockets on a port remain open for extended periods of time.
Note
File transfer may not work if you are behind a network address translation (NAT) device.
