Openwrt don’t allow android's samba server /w unusual ports while stock firmware allow


When using TP!ink C2 archer’s stock firmware,
A win10 PC connected to LAN port, /w cifs ports modified to SMB TCP 1445,
NETBIOS UDP 1137, 1138, using freeware “multi port forwarder”

Together with an unroot-ed android, using samba server app “landrive”,
connect thru wifi, /w ports modified above,
were able to share files.
The PC can ping, can FTP into, and enter the samba server app.
The unusual ports are used because of an unroot-ed android (see landrive)
(The PC can also CIFS into another win10, using normal ports)

BUT if that router is changed into an openwrt router,
No matter it is commercial GL inet BrumeW, v3.104 stock firmware (a 19.07.x),
OR DIY D1ink 842 /w latest openwrt snapshot.
The PC can ping, can FTP into, but CANNOT enter the samba server app.
!!! (BUT The PC can STILL CIFS into another win10, using normal ports)

I don’t have a USB lan for android so I cant try phone+LAN yet.
Could there be some restriction between the wifi and the LAN of an openwrt?

Help is appreciated as this is the only problem introduced after I switched into openwrt.


^—above is shorter version after I done some test, thx

old title: BrumeW don’t allow samba /w unusals port TCP1445, UDP1137/1138, thx


For an unrooted android to act as samba server, and share files to a win10,

I have to use an app called “LAN drive”, which use unusual ports:
SMB TCP 1445, and
NETBIOS UDP 1137, 1138.
(only 3 changes)


Unrooted android ------- router------- win 10 PC.

The PC side need install a freeware “multi port forwarder” for the 3 changes.

Previously I can do so with a TP!ink C2 router,
But recently I changed the router into a BrumeW, v3.104 of stock firmware,
which is a 19.07.

So I cant share files in that way now.
Hope there could be help and that could help others too.


additonal info:
The PC can ping successfully the android when using BrumeW.

The PC can even login a FTP server when using BrumeW.

so I think it’s openwrt/BrumeW blocked some ports so it allow ping, allow FTP login, but disallow the modified samba. thanks

further info:
using TP!ink, PC cifs share to PC is OK (using normal ports), PC samba phone is OK (using unusual port, in which PC use “multi port forwarder” and android use “landrive”, using the above 3 ports).

but using a GL inet BrumeW,
PC cifs share to PC is ok (using normal ports),
while PC samba phone is NOT ok (have to use the above 3 ports for landrive as is an unrooted android).

a self flashed D1ink 842 is ok with PC cifs share to PC using normal ports


latest update:
BOTH the commercial openwrt GL inet BrumeW,
and the self flashed D1ink 842 (lastest snapshot) allow-ed ping, allow-ed FTP (port 2121), also normal CIFS (PC to PC, normal ports), but NOT modified samba (PC to android, above 3 ports).

While a TP1link C2 stock firmware allowed all.

So that should be openwrt’s setting I think.


ps: in all cases, PC is connected to router’s LAN port, while phone is using wifi.

I’ll try to test what if both are using wifi, thanks.

no joy,
even PC and phone all using wifi, still can ping and FTP into, but not samba /w unusual ports. thx

Is it a SAMBA version problem?

don’t think so, definitely openwrt router blocked the above ports.

because when using TP1ink, PCs by LAN, phone by wifi,
PC-A can ping everyone, can FTP into everyone,
can use normal ports go to PC-B’s cifs.
can EVEN use the above 3 unusual ports to go to phone.

I only changed the router into BrumeW or self flashed openwrt D1ink 842.
PC-A can still ping everyone, FTP into everyone,
can use normal ports go to PC-B’s cifs,
ONLY PC-A cant use phone’s samba.

when PC-A and PC-B share files, normal ports are used,
only when PC-A and phone, that PC-A have to use multi port forwarder while phone using samba server; and both are using the above 3 unusual ports.



others say it’s my system 's problem,

others with openwrt say they can access the phone.

let me try later.


It’s all MY faults, I apologize for this.
LanDrive WORKS perfectly with openwrt.

In Verigio, in the TCP tab, there is a hard code-ed IP address,
And after trial period, you can still USE it but you cannot CHANGE it.

So I setup my Tplink within the trial period, thus working well.
With the recently bought openwrt I forget/don’t remember there is a hard code-ed
IP address, so of course openwrt 's IP will never work with that.

Very much Thank you esp to openwrt forum’s Krazeh who helped by installing the app and software for me.
Thank you everybody.

(PS seems that one have to buy the ultimate version of
Verigio for working with LanDrive, which is 20USD….)

The tutorial of landrive is here:


The limitation of trial version of verigio is here:


1 Like