[GH-ISSUE #3157] Samba 映射为445端口认证登录后无法成功建立连接 #2529

Closed
opened 2026-05-05 13:37:46 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @8ar10der on GitHub (Nov 2, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3157

Bug Description

相关issue https://github.com/fatedier/frp/issues/3105

Frps部署在Debian 11上
Frpc部署在Arch Linux上
Samba Client使用smbclient(Linux下)与Windows explorer

  • 内网内访问smb一切正常
  • 已经与VPS确认445端口没有被ban
  • 已经确认远程主机没有开启防火墙
  • 已经确认frps加权可以监听1024以下端口。

如果frpc.ini写为

[smb]
type = tcp
local_ip = 127.0.0.1
local_port = 445
remote_port = 445

那么会正常跳出认证会话,但是认证后无法建立连接。

如果修改remote port

[smb]
type = tcp
local_ip = 127.0.0.1
local_port = 445
remote_port = 10445

那么认证成功后可以正常访问smb内文件。

不记得两个月前使用frp有这个issue,近期更新后出现。查阅smb的log一切正常,没有error。

frpc Version

0.45.0

frps Version

0.45.0

System Architecture

linux/amd64

Configurations

frps.ini

[common]
bind_port = 7000
bind_udp_port = 7001
dashboard_port = 10086

token = <...>
dashboard_user = <...>
dashboard_pwd = <...>

log_file = /var/log/frp/frps.log
log_level = info
log_max_days = 3

frpc.ini

[common]
token = <...>
server_addr = <...>
server_port = <...>

admin_addr = 127.0.0.1
admin_port = 10087
admin_user = <...>
admin_pwd = <...>

log_file = /opt/frp/frpc.log
log_level = info
log_max_days = 3

[smb]
type = tcp
local_ip = 127.0.0.1
local_port = 445
remote_port = 445

Logs

frps日志

2022/11/02 11:50:01 [I] [proxy.go:179] [deb7f61c49bc5dbd] [smb] get a user connection [*.*.*.*:17541]

frps端 netstat -tunlp

tcp6       0      0 :::445                  :::*                    LISTEN      13376/frps
udp6       0      0 :::445                  :::*                                13376/frps

Steps to reproduce

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @8ar10der on GitHub (Nov 2, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3157 ### Bug Description 相关issue https://github.com/fatedier/frp/issues/3105 Frps部署在Debian 11上 Frpc部署在Arch Linux上 Samba Client使用smbclient(Linux下)与Windows explorer - 内网内访问smb一切正常 - 已经与VPS确认445端口没有被ban - 已经确认远程主机没有开启防火墙 - 已经确认frps加权可以监听1024以下端口。 如果`frpc.ini`写为 ```ini [smb] type = tcp local_ip = 127.0.0.1 local_port = 445 remote_port = 445 ``` 那么会正常跳出认证会话,但是认证后无法建立连接。 如果修改remote port ```ini [smb] type = tcp local_ip = 127.0.0.1 local_port = 445 remote_port = 10445 ``` 那么认证成功后可以正常访问smb内文件。 不记得两个月前使用frp有这个issue,近期更新后出现。查阅smb的log一切正常,没有error。 ### frpc Version 0.45.0 ### frps Version 0.45.0 ### System Architecture linux/amd64 ### Configurations frps.ini ```ini [common] bind_port = 7000 bind_udp_port = 7001 dashboard_port = 10086 token = <...> dashboard_user = <...> dashboard_pwd = <...> log_file = /var/log/frp/frps.log log_level = info log_max_days = 3 ``` frpc.ini ```ini [common] token = <...> server_addr = <...> server_port = <...> admin_addr = 127.0.0.1 admin_port = 10087 admin_user = <...> admin_pwd = <...> log_file = /opt/frp/frpc.log log_level = info log_max_days = 3 [smb] type = tcp local_ip = 127.0.0.1 local_port = 445 remote_port = 445 ``` ### Logs frps日志 ``` 2022/11/02 11:50:01 [I] [proxy.go:179] [deb7f61c49bc5dbd] [smb] get a user connection [*.*.*.*:17541] ``` frps端 netstat -tunlp ``` tcp6 0 0 :::445 :::* LISTEN 13376/frps udp6 0 0 :::445 :::* 13376/frps ``` ### Steps to reproduce _No response_ ### Affected area - [ ] Docs - [ ] Installation - [x] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [x] Client Plugin - [x] Server Plugin - [ ] Extensions - [ ] Others
Author
Owner

@8ar10der commented on GitHub (Nov 2, 2022):

又检查了一天,应该是客户端的ISP屏蔽445,我与ISP沟通后如有更新再reopen。

<!-- gh-comment-id:1301255512 --> @8ar10der commented on GitHub (Nov 2, 2022): 又检查了一天,应该是客户端的ISP屏蔽445,我与ISP沟通后如有更新再reopen。
Author
Owner

@1500256797 commented on GitHub (Mar 13, 2023):

怎么样,解决了吗?

<!-- gh-comment-id:1465910977 --> @1500256797 commented on GitHub (Mar 13, 2023): 怎么样,解决了吗?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2529
No description provided.