连接IP不正确 [英] Incorrect Connection IP

问题描述

最近，我在Dell Vostro 200上安装了Windows Server 2008 R2，并决定使用它来托管我的服务器应用程序。
我也使用no-ip ，因为我有一个动态IP（一个不会改变）。

我移植了端口8680和8787，我的服务器正在监听这些端口。

但是，无论何时客户端连接到我的服务器，它都会显示"从192.168.x.x接受连接"。

基本上，它说连接已被接受，而不是因为我的一位开发人员正试图连接。
例如，http：//www.yougetsignal.com/tools/open-ports/
fsserv.no- ip.org
8680和8787

两者都读取打开，并且在服务器上，它仍然显示"从192.168.x.x接受连接"，这也不是这种情况，因为http://www.yougetsignal.com/tools/open-ports/的IP是69.163.149.200。

这与我的客户连接有什么关系到fsserv.no-ip.org，或者因为我使用的是Server 2008 R2？
被阻止的防火墙端口是否会导致这种情况？

我正在使用2WIRE路由器我已经听说2WIRE被认为是颈部疼痛，有时候他们搞砸了什么。

任何帮助都会受到赞赏！ ：）

Hi,

Recently, I installed Windows Server 2008 R2 on a Dell Vostro 200, and decided to use that to host my server application.
I'm also using no-ip, since i have a dynamic IP (one that doesn't change).

I portforwarded ports 8680 and 8787, and my servers are listening on those ports.

However, whenever a client connects to my server, it says
"Connection accepted from 192.168.x.x"

Basically, its saying that a connection has been accepted from itself, which is not the case because one of my developers is trying to connect.

For example,
http://www.yougetsignal.com/tools/open-ports/
fsserv.no-ip.org
8680 and 8787

Both read open, and on the server, it still says "Connection accepted from 192.168.x.x", which again, is not the case because the IP of http://www.yougetsignal.com/tools/open-ports/ is 69.163.149.200.

Could this have anything to do with my client connecting to fsserv.no-ip.org, or because I am using Server 2008 R2?
Could a blocked firewall port be causing this or something?

I'm using a 2WIRE router with an at&t service plan.
I've hear that 2WIREs are known to be a pain in the neck to portforward, and sometimes they screw up or something.

Any help would be appreciated! :)

推荐答案

充其量令人困惑。 当您说端口转发时，这意味着端口正用于识别专用网络计算机。 因此192.168.X.X可以是端口转发请求的目标。 端口转发不允许您查看公共地址，因为它按照TCP / IP规范屏蔽它们，这些规范说"一切都必须在网络中进行通信，如果它不在网络中，则必须转发到网关"。 。

运行wirehark跟踪，它会告诉你所有你需要知道的事情。

Confusing at best.  When you say port forwarding that means that ports are being used to identify a private network computer.  So the 192.168.X.X can be the target of a port forward request.  Port forwarding is not going to allow you to see the public addresses as it masks them per TCP/IP specs that say "Everything must be in network to communicate, if it is not in-network it must be forwarded to the gateway...

Run a wireshark trace and it will tell you all you need to know.

这篇关于连接IP不正确的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！