Browsing WIndows Network "broken" with Symantec VPN/100 firewall appliance

From: The OTHER Kevin in San Diego (skiddz)
Date: 11/16/02 

From: The OTHER Kevin in San Diego <skiddz *AT* adelphia *DOT* net>
Date: Sat, 16 Nov 2002 09:47:33 -0800

Sigh.. The problems continue. In our last episode, it was discovered
remnants of ZAP hosed up web browsing via search engines. This time,
the problem is browsing the Windows network.

If I run a crossover cable between the two machines, browsing works
fine. We can map drives, share printers etc. NBTSTAT reports all the
usual "good" things one would expect when NetBIOS over TCP/IP is
working.

If I plug the machines back in to the firewall, all NetBIOS activity
comes to a grinding halt. Can't browse, can't map drives (even by
IP!) etc...

The firewall appliance is a Symantec VPN/100 appliance and I've
upgraded the firmware to version 15T.

Nothing in the Symantec KB mentions LAN Browsing except a small blurb
in the "Troubleshooting the Top 10 things you may have f****d up
during installation" that says "LAN Browsing functions may not work
properly" and to "verify that all computers are on the same Workgroup
or Domain. Then, ensure that File & Print Sharing is enabled on the
computers that share folders."

Well duh.. :)

Anyone seen this with one of these devices? I don't have to make a
Special Application tweak do I? As I understand it, those are port
triggers for outbound traffic and shouldn't affect stuff on the LAN
side...

Ideas anyone???