Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 685
  • Last Modified:

Wireless users cannot access network shares

Hi, I have an SBS 2003 network with a sonicwall tz180 wireless firewall/router.

Wired clients get an I.P. in the range 192.168.2.x

Wireless clients get an I.P. in the range 192.168.10.x

Wireless clients cannot access network shares on other clients (wired clients can access these shares).

I have a firewall rule allowing all traffic, regardless of port or protocol, from WLAN to LAN.

I have an I.P. helper policy allowing netbios traffic from WLAN subnets to LAN subnets.

Sonicwall support techs say that these to rules are sufficient to allow access to the shares.

I reckon this must be related to windows firewall and the resolution must be found in the domain wide windows firewall settings in the group policy editor on the SBS but after that I am stunped.

Anyone got a definitive answer?

Thanks
G
0
GazClimbs
Asked:
GazClimbs
  • 4
  • 3
1 Solution
 
suppsawsCommented:
Hello GazClimbs,

why are the wireless clients not on the same ip range?

Regards,

suppsaws
0
 
GazClimbsAuthor Commented:
Suppsaws,
  I was surprised at this myself, The sonicwall tz180 wireless is a new device puishased to replace a failed tz170. I have checked with their support techs and the WLAN interface cannot give out i.p. adresses in the same range as the WAN.

GazClimbs
0
 
suppsawsCommented:
but if you put the SBS as DHCP server, which it should be, and put on the sonicwall that the SBS is the dhcp relay server, then your wireless clients should receive their ip's in the same range as the LAN network.
you'll have to check that with sonicwall support since I don't do those devices.
0
NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

 
GazClimbsAuthor Commented:
I have found that it serves me better to have the router do the dhcp on the network, this way if for whatever reason the server is down, users can still access the internet. Up until now I have not had any issues with this approach onthe  5 SBS networks I manage, it has in fact kept the pressure slightly off during the occassional crisis, I may have to rethink, at least for this location.


Meanwhile I would really like to know how to allow access to network shares on the LAN from the WLAN, am I on the right track in thinking I can allow this in the group policy editor, windows firewall domain wide settings?

Thanks,
G
0
 
suppsawsCommented:
actually, it is nOt a good practice the get the dhcp off the sbs.
I really advise you to put dhcp on the sbs server(s). Although you cAn run an sbs without dhcp on it, it breaks alot of things when it doesn't. (connectcomputer wizard for example).
although this one is about sbs 2008, it also applies to sbs 2003:
http://sbs.seandaniel.com/2008/10/do-i-absolutely-have-to-run-dhcp-on-sbs.html

but for your issue, I am sure you can get the wifi clients on the same range, if they are not you will see more strange things, not only the share access ... don't forget this is SBS, not windows server 2003 std.
0
 
GazClimbsAuthor Commented:
There is nothing in that article to convince me that I need to invest the time required to change my setup for my other locations, though I may consider doing so as part of future maintenance or upgrades. I will of course be happy to change it for the location in question, if that is what i must do to make it work.

Thanks

G

btw the connect computer wizard works fine in these locations :)
0
 
suppsawsCommented:
I know, it's an endless discussion the dhcp part, no I'me not going to do that again :-)
It's not needed, so you can choose whatever you like off course, I'me always using the sbs as dhcp server, it's just easier.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now