NetBIOS name

RouterOS Beginner Basics
1

source information:

  1. two local network/workgroup (WITHOUT domain!): 192.168.0.0/24 and 192.168.34.0/24
  2. two servers @ win2k3 (192.168.0.1/32 (NetBIOS name: “server”) and 192.168.34.200/32 (NetBIOS name:“master”)). Their roles: fileservers, web, game, DC++ hub, shoutcast… etc. NON DNS/WINS server!
  3. routerOS between this localNET’s.

problem:

How make access through routerOS@mikrotik by NetBIOS name using setting routerOS?

at present time, every client seting up WINS server on 192.168.0.1 and 192.168.34.200.

2

Add to bridge interfaces with different networks.

3

ok, but in this case I lose control over the traffic.

4

OK, the issue here as far as I can tell (are there any other gurus who know better out there?) is that NETBIOS is a protocol that cannot be routed. And this is why you need to bridge the connections as Sergejs suggests.

BUT: There are other ways around this.

You could build a VPN between the servers, through the routes network.

You could promote the Windows Server to Domain Controllers and have them replicate properly.

I have done this successfuly for a network, where I have two college campuses and a point to point ROUTED (not bridged) mikrotik wireless link between them.

You need to make sure that your DNS and Active directory is properly configured though.

Of course this depends on what type of control you need on the traffic. You do know that the Mikrotik CAN act as a transparent traffic shaper on a bridge. Check the wiki…

Salaams,

Alex

5

NETBios is not routable