Go Premium for a chance to win a PS4. Enter to Win

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

Small office network setup problems

I just took over a small office network that has some issues. Heres the current setup:
cable modem connects to sonicwall firewall that has a static ip of 192.168.5.39, sonicwall connects to a 24port switch, switch then connects to a dlink router set at 192.168.0.1 with the gateway pointing to the sonicwall. Then the other 4 24port switches are fed by the router.  In addition we have a wireless router set as an access point.  The problem is that different workstations around the office keep losing connectivity. I can reboot the router firewall and it clears up for a an hour or so then starts dropping connection again.  What could be causing this? and better yet how can I fix it?

Thanks!
0
Bang-O-Matic
Asked:
Bang-O-Matic
  • 4
  • 3
  • 2
2 Solutions
 
Danny_LaroucheCommented:
This is a very strange network layout!!!  Not sure what the DLINK router is doing between switches!!  Which router is the DHCP server? What is your LAN subnet? 5.0 or 1.0?  What do you mean by "losing connection"? Do you mean logical connection (IP) or physical connection (switch port`s LED is off).
0
 
Danny_LaroucheCommented:
My first idea, is that there is rogue DHCP server on the network
0
 
Juan OcasioCommented:
My first question was exactly what Dayy_Larouche said;  What is the DLINK router used for?  Your internet connection is coming through the cable modem and into the firewall, but then why isn't it going directly into the switch?  Anyway is the DLink's Gateway the IP adress 192.168.5.39?  Also what is the DLINK's External IP Address?  Is is set statically (it should be).  I'm not too familiar with the sonicwall products, but if it has a DHCP server, you should disable that one and keep the DLINK DHCP server enabled (Unless you have a small enough office wherer you can assign static IP to all machines - a admin nightmare in my opinion).
0
New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

 
Bang-O-MaticAuthor Commented:
Yes I'm very confused by the setup myself, I'm no expert but it seems the dlink router could be removed and dhcp enabled in the sonicwall. Ok, I just checked and the sonicwall has dhcp enabled with a range of 192.168.5.51 - 5.250 and a lease time of 60 minutes. Also the sonicwall states: Number of LAN IP addresses allowed with this license: 50

There are approx. 70 users on this lan.

The dlink has dhcp enabled also with a range of 192.168.0.2 - 0.254
0
 
Juan OcasioCommented:
OK If you need to keep your current setup, disable the DHCP on the SonicWall as you will not need it.  Set the external IP address of your DLINK to something in the range of the SoncWalls Internal IP Range (192.168.5.51 - 5.250).  I think I see why they had this set up- the Licenses will allow for 50 internal IP addresses.  To circumvent that the last IT guy added the router and therefore only 1 internal IP address will be used at all times (it just wasn't static).  If you disable the DHCP on the SW and assign the static IP address, you should be good to go...

jocasio
0
 
Bang-O-MaticAuthor Commented:
Sounds like a plan I'll try that.  So if I turn off dhcp in the SW then will I have to assign static ip addys for the staff that must be behind the firewall?
0
 
Juan OcasioCommented:
No.  The Internal IP address of SonicWall and the external IP address of the DLINK only need to be in the same IP Range.  You already have the gateway of the DLINK pointing to the SonicWall, which is what you want.  The Gate way for your users will be the IP address (internal) of the DLINK, which I believe you said was 192.168.0.1.  This will be assigned dynamically along with the IP address by the DLINK Router.

jocasio
0
 
Juan OcasioCommented:
So what basically happens is a user on your network goes to www.thesite.com.  This request is passed to the Gateway which is 192.168.0.1.  The router says 'Can I resolve this? If it can it passes the request on.  If not it then sends the request to it's gateway (the SonicWall).  The sonic Wall then asks the same question, and because it's external interface faces the internet, it will pass on the request...

jocasio
0
 
Bang-O-MaticAuthor Commented:
ok It's up and running....much thanks for the assistance!
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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