The wireless side is a 172.x.x.x IP Range and there is not a gateway that that allows a netbios to pass from the 192.168.x.x (or whatever you use) side.
For guest users it's ok, but for us it is just not a good application. Each wireless user (employees not guests) uses the Sonicwall VPN Client to establish an Office Gateway connection. That part is good as you're using VPN technology for your security which is preferable. You do run into some killer issues with some laptops getting a good connect after coming back from suspend mode, but that's a different issue completely.
Our biggest issue is for instance a wireless laptop user is having problems. They call our office and one of our techs tunnels to that campus via VPN. Then they use a remote viewing program to jump to the laptop in question. We know that laptop is named daveslaptop for example. The problem is that we can't get there by name due to the lack of netbios transfer. Now we have to log into the DHCP Server and look for Dave's MAC Address and find his IP Address. Now we've got to try and connect by IP which is a crap shoot at best with him being on the 172 IP Range (he gets a 192. address also, but that's another story). Other factors come into play, but we're a Sonicwall Preferred Partner and I can guarantee you we've been down every road possible with Level III and R&D. It's just a bad design. Even our Channel Support Manager agreed that we needed to go back to regular access points. We could come up with lots of work arounds, but no matter what work around you came up with, it would not work as seamlessly as slapping a Linksys or Cisco box back on the network.
Don't get me wrong, the TZ170 is a good firewall and VPN device. We've been using Sonicwall since back in the early SOHO3 days. Just don't ask your heart surgeon to work on a brain tumor.
