NETBIOS support on Fortigate 100A

[#1]

I need help to enable NETBIOS support on the Fortigate unit in order to let branch office to access remotely from a Netgear VPN. I am able to ping each other but the other side cant browse the computers in the domain.

[#2]

through cli (telnet or ssh) execute : config system interface <choose appropriate interface> set netbios-forward enable save and close and your good to go.

[#3]

Couldn' t you also just open the necessary ports via the GUI, or does the Fortigate block Netbios based on the traffic type rather than the port? I have a 200 A on which I' ve added custom services: Netbios TCP - port 139 Netbios UDP - ports 137-138 I haven' t actually tried to see if it worked so I' m curious if this is possible or it has to be done via the cli. Thanks

[#4]

You can do that provided you want to enable NETBIOS on which policy and on which interface. But it doesnt not work in a encrypted policy for VPN and have to enable NETBIOS-forward thru cli.

[#5]

here' s why (by the way, the cmds on this page are incorrect) http://kc.forticare.com/default.asp?id=955&Lang=1&SID=

[UkWizard]

netbios shouldnt be blocked, the problem is probably DNS related, get the remote clients to use the AD DNS at the main site, this may resolve it. Presuming the remote clients are members of the domain.

[UkWizard]

actually, thinking about it, you say " cant browse the computers in the domain" if you are talking about the clients, rather than the servers, then it could be the clients do not have the firewall set as the default route... if you cannot map a network drive to any of the remote machines, then there is a bigger issue with the vpn connectivity as a whole.

[#8]

My problem is solved after I enable the NETBIOS-forwarding. I need this service as we have a NT domain on the remote site which does not have WINS support.