How do i set up the router so that computers from 192.168.1.x can access computers from network 192.168.0.x and view computer workgroup on each system.
(2) Be able to share files and folder, and also be able to print on a printer installed on one of the system e.g(192.168.0.56)

Thank you!

Routers do not normally forward b-node broadcasts. NetBIOS over TCP/IP uses b-node broadcasts for name resolution and registration on your local LAN segment. If you want your router to forward b-node broadcasts, you must enable UDP ports 137 and 138. By enabling UDP ports 137 and 138 on your router, a name query broadcast with the destination NetBIOS name can be forwarded.

A b-node broadcast is a UDP datagram. If these broadcast datagrams pass through your router, it will greatly increase traffic on your internetwork and decrease performance. Not every router can forward b-node broadcasts, and usually this function is disabled on routers that can forward the broadcasts. Active directory and Windows domains take care of this problem, but the systems have to be a part of that in order for you to browse those domains.

@THGTanx,How do I go about this on MK x86 RoS v3.11,Pls explain in detail.

I don't know if it's even possible to convert broadcast messages into directed-broadcast or unicast messages in RouterOS. Cisco routers have the IP Helper Address feature to take care of it.

Browser service or Computer Browser Service is a feature of Microsoft Windows to let users easily browse and locate shared resources in neighboring computers. This is done by aggregating the information in a single computer 'Browse Master' (or 'Master Browser'). All other computers contact this computer for information and display in the Network Neighborhood window.

Browser service runs on mailslot / SMB and thus can be used with all supported transport protocol such as NetBEUI, IPX/SPX and TCP/IP. Browser service relies heavily on broadcast, so it is not available across network segments separated by routers. Browsing across different IP subnets need the help of Domain Master Browser, which is always the Primary Domain Controller (PDC). Therefore browsing across IP subnets is not possible in a pure workgroup network.

I'm sorry, but you need either a Active Directory Server or a Windows Domains Controller to browse network resources across subnets. You can of course use network resources across subnets by IP instead of names. You can also setup a DNS server to take care of the name resolution process, but you can never browse workgroups on multiple subnets.

What we've done to combat this issue (sharing between subnets) is to have static computer names/ip addresses, and static printer ip addresses.

We also have a main fileserver with a static IP address.

What I've done on all the computers is manually map a network shared drive based on the IP address.
This works fine across subnets and what not, and really speeds up the whole file finding process. Now instead of hunting through "My Network Places -> Entire Network -> Microsoft Windows Network -> [Workgroup name] -> [server name] -> [share name]", everyone just clicks on the "X" drive, then folder.

It is way faster.

Also, putting a terminal server at the main office and letting people RDP in to open large files works quite well too, but costs a little more.

To add printers, just type in the IP address of the sharing computer in the Windows Explorer address bar, then find the printer and right click on it, or however you normally install remote printers. Once installed it should work fine.

@Suthern,Tanx for your response.Are u using MikroTik router on your network?