[GH-ISSUE #705] 网络中断后，windows客户端没有重新协商端口 #555

New issue

Closed

opened 2026-05-05 12:21:49 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 12:21:49 -06:00

Owner

Originally created by @carlsue on GitHub (Apr 12, 2018).
Original GitHub issue: https://github.com/fatedier/frp/issues/705

Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly.
(为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。)

Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST

What version of frp are you using (./frpc -v or ./frps -v)?
0.16.1

What operating system and processor architecture are you using (go env)?
server ： windows server 2016 dc
client：Windows 10 1709

Configures you used:
client-----------------------------------------------------------
`[common]
server_addr = aaa
server_port = 2025
privilege_token = 65432
protocol = kcp
admin_port = 7400
admin_user =
admin_pwd =

[miix4-rdp]
type = tcp
local_ip = 127.0.0.1
local_port = 3389
remote_port = 0`

server-------------------------------------------------------------
[common]
bind_addr = 0.0.0.0
bind_port = 2025
bind_udp_port = 2026
kcp_bind_port = 2025
authentication_timeout = 0

privilege_allow_ports = 4025-4045

dashboard_addr = 0.0.0.0
dashboard_port = 7500

dashboard_user = admin
dashboard_pwd =

subdomain_host =

log_file = ./frps.log
log_level = info
log_max_days = 2
privilege_token = 65432
tcp_mux = true

Steps to reproduce the issue:
1.重启server端操作系统后运行frps
or
2.客户端重启出口路由器
3.结果是客户端还是运行在以前的端口，没有重新协商新端口

Describe the results you received:
客户端查看状态显示running

服务端，没有上面的name

Describe the results you expected:
客户端要能重新协商端口，让我能继续使用

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Originally created by @carlsue on GitHub (Apr 12, 2018). Original GitHub issue: https://github.com/fatedier/frp/issues/705 Issue is only used for submiting bug report and documents typo. If there are same issues or answers can be found in documents, we will close it directly. (为了节约时间，提高处理问题的效率，不按照格式填写的 issue 将会直接关闭。) Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST **What version of frp are you using (./frpc -v or ./frps -v)?** 0.16.1 **What operating system and processor architecture are you using (`go env`)?** server ： windows server 2016 dc client：Windows 10 1709 **Configures you used:** client----------------------------------------------------------- `[common] server_addr = aaa server_port = 2025 privilege_token = 65432 protocol = kcp admin_port = 7400 admin_user = admin_pwd = [miix4-rdp] type = tcp local_ip = 127.0.0.1 local_port = 3389 remote_port = 0` server------------------------------------------------------------- [common] bind_addr = 0.0.0.0 bind_port = 2025 bind_udp_port = 2026 kcp_bind_port = 2025 authentication_timeout = 0 privilege_allow_ports = 4025-4045 dashboard_addr = 0.0.0.0 dashboard_port = 7500 dashboard_user = admin dashboard_pwd = subdomain_host = log_file = ./frps.log log_level = info log_max_days = 2 privilege_token = 65432 tcp_mux = true **Steps to reproduce the issue:** 1.重启server端操作系统后运行frps or 2.客户端重启出口路由器 3.结果是客户端还是运行在以前的端口，没有重新协商新端口 **Describe the results you received:** 客户端查看状态显示running ![image](https://user-images.githubusercontent.com/17507066/38691228-d75b9728-3eb2-11e8-894d-c57ea04d2c88.png) 服务端，没有上面的name ![image](https://user-images.githubusercontent.com/17507066/38691250-ea233140-3eb2-11e8-8a58-7f24e1bd59f8.png) **Describe the results you expected:** 客户端要能重新协商端口，让我能继续使用 **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**

gitea-mirror closed this issue

2026-05-05 12:21:50 -06:00

gitea-mirror commented

2026-05-05 12:21:52 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 19, 2018):

remote_port = 0 时，端口由服务端随机分配，但是对于同一个 proxy，如果中间有断开连接，重连后会尽量使用之前的 port。

@fatedier commented on GitHub (Apr 19, 2018): `remote_port = 0` 时，端口由服务端随机分配，但是对于同一个 proxy，如果中间有断开连接，重连后会尽量使用之前的 port。