Hello everyone,
I’m having some issues with netbios in my network. I swapped an old drytek for new ccr recently, and step by step adjusting every little thing that pops up. Today i encountered problem with discovering host names. I can send/recieve ping (both client and server side), connect via ip (ie. \192.168.10.20 connects me without even a slightest choke) but \server1 not (even if it’s the hostname of 192.168.10.20).
I thought this might be due to blocked ports, however adding
does not help.
Before you point it out: i posted tcp3389 here because this was the first thing that i noticed wasnt working via hostname. It does via ip with this rule.
But when instead of plugging servers right into the bridge, i connect them like this:
it works again.
I thought this might be due to some ARP tables being stuck, or whatever, but no luck after resetting, replugging etc…
I even disabled the whole FW for testing, but still no luck.
Correct me if i’m worng, but this might also explain why whenever i connect via vpn, i cant map net drives…?
(everything else works fine on vpn, even web forwarding, and local www servers)
I’m almost 100% sure i’m missing just one small detail, to fix two things at once, but i’m out of ideas what to look for:(
Any hints what i might’ve missed? Did i forget about some NATting transparency or priorities? Does rstp have some unusal config for this?
I’m sorry if i posted this in wrong subforum, wasnt’s sure where to put it.
How is netbios (CIFS) service provided? Samba? Windows Server? Are you running an AD?
Correct me if i’m worng, but this might also explain why whenever i connect via vpn, i cant map net drives…?
(everything else works fine on vpn, even web forwarding, and local www servers)
Cannot you map them even using \192.168.10.20\Share as UNC (i.e. including IP on it)?
Yes, i can map them using ip address, but ~80laptops in my network run via hostname- and to do so, i’d have to intercept every single one of them, to remap hostname to ip.
I’d really prefer finding a solution to the core of the problem instead of meddling with some workarounds:)
Edit: Also, some of running 3rd party services use hostnames instead of IPs, it’s not just about mapping drives.
While layering WINS on may resolve the situation, it doesn’t explain why the problem doesn’t appear locally on the layer 2 only switches.
Op, are you able to post a full config dump. Feel free to obfuscate (alter) any passwords and IP addresses. As long as you aren’t routing anything and just bridging it through it should work. That said, netbios bro! Gotta get you some AD goodness with DNS.
Are you using NetBios over NBF? Probably not if you have any computers newer than XP. Edit the properties for IPv4, go to Advanced > WINS. Enable NetBios over TCP/IP on both a workstation and server. Does it work then?
Use Winbox > Tools > Packet Sniffer, try resolving a hostname and then post the capture file on this thread.
The filter rules you set up don’t impact slave interfaces, only interfaces in the same bridge. You can remove those rules. ARP relates to mapping IPs to MAC addresses, so it’s not an ARP issue. It’s a hostname resolution issue. DNS has long been preferred over NetBios resolutions. You can use DHCP + DNS Suffixes (and a DNS server), this way you don’t have to update all computers.
NetBios only works on the same broadcast domain. It’ll never work over a VPN (unless maybe if all the clients traffic is being routed over the VPN and you’re not using NetBeui).
The problem as Van9018 points is he is interconnecting two networks, so no contiguous L2, not same broadcast domain, and… no netbios resolution, hence the need for WINS at least.
Unless you run XP or windows 7/Os X Lion/Mountain Lion, later OSes all use either SMB2 or SMB3 protocol which is TCP based and will use WINS, no need to specify NetBios over TCP/IP; just hand over the WINS server with the DHCP option and you’ll be set.
Best approach is having two servers or each network to act as WINS servers and interconnect them so that they use each other as resolvers for the remote network WINS server.
Having the full export will help certainly, this could be also due to same horizon at ports added at the VPN bridge.
