Can not access Samba SMB shares across VLANS (All TP-Link Omada Networking Gear)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Can not access Samba SMB shares across VLANS (All TP-Link Omada Networking Gear)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Can not access Samba SMB shares across VLANS (All TP-Link Omada Networking Gear)
Can not access Samba SMB shares across VLANS (All TP-Link Omada Networking Gear)
2023-05-03 02:53:00
Model: SG2008P   OC200   ER605 (TL-R605)  
Hardware Version: V3
Firmware Version: 3.0.4 Build 20221130 Rel.42340

Hello Everyone,

 

I really hope someone could guide me in the right direction and any assistance is greatly appreciated.

 

Long story, short. I am having zero luck trying to access the Samba share on my OpenMediaVault (OMV) that is on my "Servers" VLAN - 20 at Static IP 10.1.20.50 from any device on my "Main" VLAN - 10. I have absolutely no issues if the OpenMediaVault Server and the other devices are on the same VLAN.

 

I have been working on this for the past two weeks and I have done tons of googling and nothing I found has worked. I have tried just about every possible combination of ACL's (Gateway & Switch), as well as profile (IP Groups & IP Group/Port).

 

The way things currently sit since I restored to factory defaults today, is as follows. I can currently Ping the OMV Server (10.1.20.50 - VLAN 20) from my MacBook Pro (10.1.10.5 - VLAN 10) and vice versa. I can also access the OMV Web GUI (10.1.20.50:5050 - VLAN 20) from my MacBook Pro (10.1.10.5 - VLAN 10).

 

The only thing I have done to my system since I restored today is configured my network gear and OMV server for static IP's, setup my VLAN's again, as well as setup a WiFi AP SSID's for each VLAN for testing purposes and all appears to be well for basic Out-Of-The-Box functionality. I opted to leave everything else sitting as default to help with trouble shooting and guidance from you all.

 

Here is some basic info related to my setup.

 

Hardware:

TP-Link Omada Controller: OC200 2.0 (2.7.7 Build 20221206 Rel.58608)

TP-Link Router: ER605 v2.0 (2.1.2 Build 20230210 Rel.62992)

TP-Link Switch: TL-SG2008P V3.0 (3.0.4 Build 20221130 Rel.42340)

TP-Link Access Point: EAP225 v3.0 (5.1.0 Build 20220926 Rel. 62456)

 

Networks:

LAN – 10.1.1.1/24

Main – 10.1.10.1/24

Servers – 10.1.20.1/24

IoT – 10.1.30.1/24

 

Device List / VLAN:

LAN (Default VLAN - 1)

Controller (OC200 2.0) - Static IP: 10.1.1.254

Router (ER605 V2) - Static IP: 10.1.1.1

Switch (TL-SG2008P V3.0) - Static IP: 10.1.1.100

Access Point (EAP225 v3.0) - Static IP: 10.1.1.150

 

Main (VLAN - 10)

MacBook Pro – Dynamic IP: 10.1.10.5

Servers (VLAN - 20)

OpenMediaVault (RaspberryPi 4) – Static IP: 10.1.20.50

IoT (VLAN - 30)

Nothing Assigned yet.

 

Networking Gear Basic Config:

 

Router (ER605 V2) Configuration:

Static IP: 10.1.1.1

WAN: Starlink

WAN/LAN1: AT&T

LAN2 Port: To Switch (TL-SG2008P V3.0)

VLAN LAN – 10.1.1.1/24

VLAN Main – 10.1.10.1/24

VLAN Servers – 10.1.20.1/24

VLAN IoT – 10.1.30.1/24

 

Switch (TL-SG2008P V3.0) Configuration:

Port 1: Profile (All), to Omada Controller

Port 2: Profile (All), to Wireless AP

Port 3: Empty

Port 4: Profile (Main – VLAN 10), to MacBook Pro (10.1.30.10)

Port 5: Empty

Port 6: Empty

Port 7: Profile (Servers – VLAN 20), to OpenMediaVault (10.1.20.50)

Port 8: Profile (All), to Wireless AP

 

Access Point (EAP225 v3.0) Configuration:

Static IP: 10.1.1.150

SSID – RvNetAdmin (VLAN 1 - Default)

SSID – RvNet (VLAN 10 - Main)

SSID – RvNetServers (VLAN 20 - Servers)

SSID – RvNetIoT (VLAN 30 - IoT)

I currently have one AP for each VLAN for testing.

 

Current Configuration Notes:

All devices have been factory reset.

NO Gateway, Switch or EAP ACL’s

NO Profile Groups (other than the default “IPGroup_Any”)

NO mDNS

NO UPnP

IGMP Proxy, IGMP Version: v2, IGMP Interface: WAN

  0      
  0      
#1
Options
3 Reply
Re:Can not access Samba SMB shares across VLANS (All TP-Link Omada Networking Gear)
2023-05-03 12:06:56

  @bfriendjr 

 

So, the inter-VLAN routing is working and there are no ACLs configured on either the switch or router, right? If that's the case, there isn't really anything on the router or the switch that would cause that issue. Perhaps, you have a firewall on the server or Mac that disallows SMB from remote subnets.

Kris K
  0  
  0  
#2
Options
Re:Can not access Samba SMB shares across VLANS (All TP-Link Omada Networking Gear)
2023-05-04 05:02:31
It's my understanding based on what I read today that SMB does not allow browsable functionality across VLANS. I was able to connect my shares by manually connecting to the server. I guess this has something to do with SMB being older technology. Here is what I had to do to connect via my MacBook. smb://10.1.20.50/files If anyone knows of a workaround, please let me know because I would prefer that the shares are broadcasted and browsable access VLANS.
  0  
  0  
#3
Options
Re:Can not access Samba SMB shares across VLANS (All TP-Link Omada Networking Gear)
2023-05-04 06:56:05 - last edited 2023-05-04 12:11:23

  @bfriendjr 

 

Is that Samba SMB the old version of SMB? I believe it was using NetBIOS/NetBEUI. I all forgot about those old days. However nowadays, SMB uses TCP/IP which is a routable protocol. I have SMBv3 enabled on my Synology NAS in the 192.168.90.0/24 subnet. I can still access the NAS shares from my WIN11 laptop even if it is connected to the 192.168.10.0/24 network.  

Kris K
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 1185

Replies: 3

Related Articles