作者 主題: MSN Messenger  (閱讀 11669 次)

0 會員 與 1 訪客 正在閱讀本文。

...

  • 酷學園旁聽生
  • 俺是博士!
  • *****
  • 文章數: 5607
    • 檢視個人資料
MSN Messenger
« 於: 2002-01-17 13:06 »
我和朋友都是使用MSN Messenger和HiNet ADSL,另外都還外加IP分享器。
平常都只是聊天,但有時會有傳檔的需求,卻始終無法傳過,據說是因為MSN傳檔時使用特殊的PORT,而分享器會阻擋所致。
我們的分享器都可以設定開啟特殊的PORT,但我在MSN的程式、網站上都找不到相關的訊息可以告訴我它使用的PORT數。
不曉得有沒有那位高手可以提供相關訊息,讓我們可以正常使用?
謝謝!

Anonymous

  • 訪客
MSN Messenger
« 回覆 #1 於: 2002-01-17 23:19 »
不是說 PORT 給擋了﹐而是要設定分享器要如何將 request 送進來﹐因為這類連線多是從外至內﹐事先很難幫您建立轉遞。

Anonymous

  • 訪客
MSN Messenger
« 回覆 #2 於: 2002-01-19 09:42 »
難道沒有其他的方法了,鳴鳴鳴,要跟遠方的朋友通話說

Anonymous

  • 訪客
MSN Messenger
« 回覆 #3 於: 2002-01-19 10:35 »
這個最好要問廠商才知道是否有相關模組可以解決﹖

Anonymous

  • 訪客
MSN Messenger
« 回覆 #4 於: 2002-01-19 14:19 »
引用

在 2002-01-19 10:35, netman 寫了:
這個最好要問廠商才知道是否有相關模組可以解決﹖

test

protech

  • 活潑的大學生
  • ***
  • 文章數: 322
  • 性別: 男
    • 檢視個人資料
MSN Messenger
« 回覆 #5 於: 2002-01-21 11:36 »
NAT vs MSN Messenger----What's the solution for them??
這是官方的網站文件,不知有網友可以分享這方面的經驗嗎?
文件有提到 UPnP protocol,以 redhat 7.1 完成的 nat 有支援此項嗎?

以下摘自微軟網站 ( http://www.microsoft.com/windowsxp/pro/techinfo/deployment/natfw/natwinmes.asp )
------------------------------------------------------------------
This section addresses issues and configurations for NAT devices.

Problems Caused by NAT Devices
The specific problems that NAT devices cause in relation to Windows Messenger features include:

Clients behind a NAT device usually have a private IP address assigned to them. This address is translated to and from a public IP address and port by the NAT device. In several cases this private address is presented in a message to a Windows Messenger peer to enable the peer to contact the client. The address is invalid for this use and the translated address must be used instead.
There are several cases where port mappings must be made at the NAT device to present an address and port to an external client and have it map to the appropriate internal client.
In some cases where static ports are used for a particular feature, only a single client behind the NAT can use that feature.
Working With Different NAT Device Configurations
The following section discuss issues related to different NAT device configurations:

UPnP–enabled NAT Devices
The UPnP forum contains several working committees, including a working committee specific to Internet gateway devices. This group is responsible for defining the specifics of UPnP support for these devices which include NAT and firewall devices. This group has defined a standard for ICS and NAT network traversal using UPnP.

NAT and firewall devices that support this standard can be detected and controlled using UPnP protocols. UPnP can be used by clients to read and configure port mappings. Windows XP ICS and ICF support this standard. Other vendors of network edge devices have also announced support of this standard, including ARESCOM Inc., Buffalo Technologies Corp., D–Link Systems Inc., Intel Corp., Linksys Group Inc. and NetGear Inc.

Windows XP also provides client support for UPnP and application program interfaces (API) specifically designed for applications to detect and leverage UPnP–enabled NAT and firewall devices on a network. Windows Messenger in Windows XP uses these APIs to achieve the following:

Detect whether the Windows Messenger client is behind a NAT device, and if so retrieve the translated address to send to its peer. This solves several problems seen above.
Obtain a port–mapping for dynamically allocated ports to be used for signaling, such as required by a SIP session configuration. This allows signaling by the external client to reach its destination.
Obtain mappings for the dynamic ports used by media streams — including those used for AV, AS and WB.
Detect whether the Windows Messenger peer is behind the same NAT device. If so, the real addresses of the peer are retrieved and the peers can communicate directly.
Note Support for UPnP clients of NAT traversal is currently available for previous versions of Windows—(Windows 98, 98SE, ME). This support is distributed by running the Network Setup Wizard that ships in Windows XP.

Non–UPnP NAT Devices
Windows Messenger peers, separated by a NAT device that cannot be detected, should be able to use IM and Presence. This is true whether the network service being used is .NET Messenger, Exchange IM, or a SIP solution. Clients using SIP servers also work because logic has been added to the client to ensure communication when the server is opened.

Issues arise, as described earlier in this article, with the other features of Windows Messenger. The following points relate to those issues:

IM and Presence are implemented through a mediating server with a direct TCP connection initiated by the client when using .NET Messenger or Exchange IM. This should not present any NAT or firewall issues. Sessions or connections initiated by clients external to the NAT device will not succeed because the internal client cannot provide the NAT–translated address to the peer. In the case of AV this applies to calls made by the internal client to the external client, because the external client is the one initiating the SIP session. If the external client calls the internal client, the failure occurs later in the process. The internal client can send the SIP invite to the external client, but the address passed in this invite is incorrect.
Calls made between peers on the same side of the NAT device should work.
An application layer gateway (ALG) for SIP may alleviate some of these problems. ALGs can be used as an application level filter for specific applications and protocols.
Cascading NAT Devices
Even if the edge of your network doesn't use a NAT device, or uses a UPnP–aware NAT device, Windows Messenger AV communication can be defeated by a cascading NAT scenario. In this scenario, another NAT device exists in the path between you and the Windows Messenger client you are communicating with, and this NAT device is not under the control of either client. This can occur if your Internet service provider (ISP) also uses NAT technology in their network. This is not a common occurrence. If you suspect this situation, contact your ISP to verify the issue and discover possible workarounds.


kan

  • 懷疑的國中生
  • **
  • 文章數: 48
    • 檢視個人資料
MSN Messenger
« 回覆 #6 於: 2002-01-21 21:09 »
為何不用Yahoo的即時通?在NAT下傳檔,語音都沒問題

KevinLing

  • 活潑的大學生
  • ***
  • 文章數: 292
    • 檢視個人資料
MSN Messenger
« 回覆 #7 於: 2002-01-21 23:51 »
那是因為 YAHOO Messenger 是用 port#80 (應該也是 scheduling 向 server query 吧). 至於 IP 分享器下不能用, 小弟就不了解了, 因為 MSN 我也沒用過. 這台 SAR-7104 倒是可以用 (http://www.routers.com.tw)

enochlee

  • 可愛的小學生
  • *
  • 文章數: 22
    • 檢視個人資料
MSN Messenger
« 回覆 #8 於: 2002-02-03 12:46 »
昨晚剛從原來的固五換成1.5m的固一,逼的我一定要架nat了(之前太懶了),但msn語音聊天竟然不能用了,我只查到msn語音通訊tcp和udp都是6901,還沒試著打開這個port(其實是不會啦),是否依netman兄的icq範例,將port4000直接改為6901即可,另yahoo即時通,如果是加入朋友在chat網頁上的聊天室不會有問題,但如果二人都是用即時通而不是用chat網頁時,對方講一個字就會關閉語音伺服器了(但是我講話對方聽的到,這個問題忘了在哪裡看過,這几天找msn通過nat的資料,眼睛快脫窗了)。
p.s. 我是用2.2.16的核心,ipchain,還是要把系統升為rh7.2呢

Anonymous

  • 訪客
MSN Messenger
« 回覆 #9 於: 2002-02-03 16:59 »
我不清除 msn 是否有語音模組提供~~
如果繼續用 ipchains ﹐或野i以參考我舊文章﹐將 h323 模組編起來﹐然後改用 netmeeting ~~

用 iptables 也沒問題﹐請參考新文章。

lienita

  • 可愛的小學生
  • *
  • 文章數: 1
    • 檢視個人資料
MSN Messenger
« 回覆 #10 於: 2002-02-04 16:56 »
要不要用Yahoo的即時通也要看周圍的朋友是使用什麼?我的朋友十之八九都是使用MSN,當然只能使用MSN。
我們大家都有寬頻,也都有多部電腦,平常傳文字訊息都沒問題,但只要使用MSN的其他弁鈳ㄓㄞ鄍峞C

enochlee

  • 可愛的小學生
  • *
  • 文章數: 22
    • 檢視個人資料
MSN Messenger
« 回覆 #11 於: 2002-02-04 22:01 »

Chinese GNU/Linux Extensions for Red Hat (Atayal)
Kernel 2.2.16-22 on an i686
Desktop/     ipmasqadm-0.4.2-3.i386.rpm  playlist.cgi
Emacs        licq-1.0.3-1.i386.rpm       webmin-0.86.rpm
Mail/        mail/                       ymessenger-0.93.0-1.i386.rpm
News/        mbox
de530tx.zip  nsmail/
[root@ns1 /root]# ipmasqadm autofw -A -r tcp 5001 5001 -h 192.168.1.2

之前yahoo即時通語音通話有問題,加了上面一行後,就沒問題了,但是msn仍然不行說,能否請netman兄或其他先進看一下,下列語法是否有問題,謝謝!
[root@ns1 /root]# ipmasqadm autofw -A -r tcp 6901 6901 -h 192.168.1.2
[root@ns1 /root]# ipmasqadm autofw -A -r udp 6901 6901 -h 192.168.1.2

Anonymous

  • 訪客
MSN Messenger
« 回覆 #12 於: 2002-02-04 22:09 »
不同的程式所用的 socket 都不一樣哦~~
同樣的設定適用於 A ﹐未必適用於 B 。

Anonymous

  • 訪客
MSN Messenger
« 回覆 #13 於: 2002-02-04 22:12 »
ipmasqadm autofw -A -r tcp 5001 5001 -h 192.168.1.2

請問上面這行,如果改用iptables要如何下呢?如果不下這行,在yahoo即時通
會有什麼不能用的情況呢?謝謝

enochlee

  • 可愛的小學生
  • *
  • 文章數: 22
    • 檢視個人資料
MSN Messenger
« 回覆 #14 於: 2002-02-04 22:27 »
1.iptable還不會,sorry!
2.沒下這行之前,我方語音都沒問題,對方也都聽的見,但對方一講話,語音伺服器就會關閉重開,不知道別人會這樣嗎?

enochlee

  • 可愛的小學生
  • *
  • 文章數: 22
    • 檢視個人資料
MSN Messenger
« 回覆 #15 於: 2002-02-04 22:28 »
p.s.我是在這個網站找到的相關資料
http://www.tsmservices.com/masq/

Anonymous

  • 訪客
MSN Messenger
« 回覆 #16 於: 2002-02-04 22:44 »
找到了,哈哈哈....(不過還沒試)
msn的modlue
http://home.tig-grr.com/mmsmasq.tar.gz
msn的module的source
http://www.e-infomax.com/ipmasq/files22/mmsmasq.tar.gz


善用搜尋,好處多多,太多層了,我只記得是從一個德國的網站進去的
這個也不錯

http://www.e-infomax.com/ipmasq/

Anonymous

  • 訪客
MSN Messenger
« 回覆 #17 於: 2002-02-04 22:46 »
引用

在 2002-02-04 22:12, Anonymous 寫了:
ipmasqadm autofw -A -r tcp 5001 5001 -h 192.168.1.2

請問上面這行,如果改用iptables要如何下呢?如果不下這行,在yahoo即時通
會有什麼不能用的情況呢?謝謝


如果換成 iptables 大概會變成這樣﹕
iptables -t nat -A PREROUTING -p tcp -d $RXT_IF --dport 5001 -j DNAT
 --to-destination 192.168.1.2

p.s. 會不會 iptables 不必緊張~~ 只要對底層的網路原理都清楚的話﹐很快就會﹐看完如下文章就可以了﹕
http://www.study-area.org/linux/servers/linux_nat.htm

enochlee

  • 可愛的小學生
  • *
  • 文章數: 22
    • 檢視個人資料
MSN Messenger
« 回覆 #18 於: 2002-02-04 22:48 »
啊!我怎麼給他變成路人甲了說.....,要去試這個module了
請教一下,應該可以直接probe吧

enochlee

  • 可愛的小學生
  • *
  • 文章數: 22
    • 檢視個人資料
MSN Messenger
« 回覆 #19 於: 2002-02-04 23:07 »

[root@ns1 mmsmasq]# ls
Makefile  ip_masq_mms.c
[root@ns1 mmsmasq]# make
gcc -O2 -Wall -fomit-frame-pointer -fno-strength-reduce -pipe -m386 -include /us
r/src/linux/include/linux/modversions.h -I/usr/src/linux/include -D__KERNEL__ -D
MODULE -DMODVERSIONS -DCPU=386 -DEXPORT_SYMTAB -c ip_masq_mms.c
In file included from ip_masq_mms.c:19:
/usr/src/linux/include/linux/module.h:145: `get_module_symbol_R_ver_str' declared as function returning a function
/usr/src/linux/include/linux/module.h:145: warning: parameter names (without types) in function declaration
In file included from /usr/src/linux/include/linux/sched.h:20,
                 from /usr/src/linux/include/linux/mm.h:4,
                 from /usr/src/linux/include/linux/slab.h:14,
                 from /usr/src/linux/include/linux/malloc.h:4,
                 from /usr/src/linux/include/linux/skbuff.h:132,
                 from ip_masq_mms.c:22:
/usr/src/linux/include/linux/smp.h:77:49: warning: "smp_num_cpus" redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:28:1: warning: this is the location of the previous definition
/usr/src/linux/include/linux/smp.h:83:26: warning: "smp_call_function" redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:118:1: warning: this is the
location of the previous definition
In file included from /usr/src/linux/include/linux/sched.h:74,
                 from /usr/src/linux/include/linux/mm.h:4,
                 from /usr/src/linux/include/linux/slab.h:14,
                 from /usr/src/linux/include/linux/malloc.h:4,
                 from /usr/src/linux/include/linux/skbuff.h:132,
                 from ip_masq_mms.c:22:
/usr/src/linux/include/asm/processor.h:96:18: warning: "cpu_data" redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:6:1: warning: this is the location of the previous definition
In file included from /usr/src/linux/include/linux/interrupt.h:51,
                 from /usr/src/linux/include/linux/netdevice.h:334,
                 from /usr/src/linux/include/net/ip.h:29,
                 from /usr/src/linux/include/net/checksum.h:31,
                 from /usr/src/linux/include/net/tcp.h:24,
                 from ip_masq_mms.c:27:
/usr/src/linux/include/asm/hardirq.h:23:24: warning: "synchronize_irq" redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:138:1: warning: this is thelocation of the previous definition
In file included from /usr/src/linux/include/linux/interrupt.h:52,
                 from /usr/src/linux/include/linux/netdevice.h:334,
                 from /usr/src/linux/include/net/ip.h:29,
                 from /usr/src/linux/include/net/checksum.h:31,
                 from /usr/src/linux/include/net/tcp.h:24,
                 from ip_masq_mms.c:27:
/usr/src/linux/include/asm/softirq.h:75:23: warning: "synchronize_bh" redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:142:1: warning: this is the location of the previous definition
In file included from ip_masq_mms.c:29:
/usr/src/linux/include/net/ip_masq.h:319:26: warning: nothing can be pasted after this token
/usr/src/linux/include/net/ip_masq.h:322:25: warning: nothing can be pasted after this token
/usr/src/linux/include/net/ip_masq.h:325:29: warning: nothing can be pasted after this token
{standard input}: Assembler messages:
{standard input}:9: Warning: Ignoring changed section attributes for .modinfo
make: *** [ip_masq_mms.o] Error 1
[root@ns1 mmsmasq]#
請問這是當初linux沒灌好,有關programing的東東沒裝的關係嗎?