Sonicwall TZ 210 setting up a block of IPs from ISP
I am running a Sonicwall TZ 210 with SonicOS Enhanced
We have a block of IP addresses from our ISP.
One of the IP addresses are being utilized on our Sonicwall lets call it 99.88.77.146.
The other is configured on a D-Link router lets call it 99.88.77.150.
We currently have clients accessing two servers via the D-Link router. However randomly during the day our clients will lose connection even though we are still able to access the internet using the connection from the Sonicwall. The only way to resolve the problem is to power cycle the ISP's modem, but the frequency that we are having to do this has increased dramatically leading me to believe we may have some possible hardware failure involved.
As part of the troubleshooting process I have tried to get rid the D-Link and configure the Sonicwall to handle all of the traffic for both IP addresses, which I believe is the way it should have been set up originally. However, all of my attempts to make this work have failed.
I've created the services to the ports that both of the servers need, created the service groups. And have gone through the public server wizard to configure the address objects, NAT policies, and access rules but it is not working.
According to the posts I have read, once you have one WAN port configured with an IP from the block of IP addresses assigned that what I have done is all that you have to do. Do I need to get my ISP involved and have them replace the modem?
We have a block of IP addresses from our ISP.
One of the IP addresses are being utilized on our Sonicwall lets call it 99.88.77.146.
The other is configured on a D-Link router lets call it 99.88.77.150.
We currently have clients accessing two servers via the D-Link router. However randomly during the day our clients will lose connection even though we are still able to access the internet using the connection from the Sonicwall. The only way to resolve the problem is to power cycle the ISP's modem, but the frequency that we are having to do this has increased dramatically leading me to believe we may have some possible hardware failure involved.
As part of the troubleshooting process I have tried to get rid the D-Link and configure the Sonicwall to handle all of the traffic for both IP addresses, which I believe is the way it should have been set up originally. However, all of my attempts to make this work have failed.
I've created the services to the ports that both of the servers need, created the service groups. And have gone through the public server wizard to configure the address objects, NAT policies, and access rules but it is not working.
According to the posts I have read, once you have one WAN port configured with an IP from the block of IP addresses assigned that what I have done is all that you have to do. Do I need to get my ISP involved and have them replace the modem?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Unfortunately the changes did not resolve the problem. I am still unable to access the server via the 99.88.77.150 outside IP address when using the SonicWall.
The WAN port in configured properly, at least to my knowledge. I am unable to access the configuration of the modem so I am unsure how it is configured.
The WAN port in configured properly, at least to my knowledge. I am unable to access the configuration of the modem so I am unsure how it is configured.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was testing access from outside of our network.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Part of the problem could be because the servers we are routing to are on a separate network IP scheme (which I do not understand why it was done that way), but I should at least be able to ping 99.88.77.150.
1) X1
IP: 99.88.77.146
Subnet: 255.255.255.248
2) X0
IP: 192.168.0.253
Subnet: 255.255.255.0
3) Public IP
99.88.77.150
4) Private IP
172.17.2.5 and
172.17.2.3
5) Ports
7014 TCP&UDP
7013 TCP&UDP
The Sonicwall is connected directly to a cable modem (SMC8014W-G). The modem does not appear to be in bridged mode. If you connect to it you get an IP address assigned by the DHCP server on the SMC.
1) X1
IP: 99.88.77.146
Subnet: 255.255.255.248
2) X0
IP: 192.168.0.253
Subnet: 255.255.255.0
3) Public IP
99.88.77.150
4) Private IP
172.17.2.5 and
172.17.2.3
5) Ports
7014 TCP&UDP
7013 TCP&UDP
The Sonicwall is connected directly to a cable modem (SMC8014W-G). The modem does not appear to be in bridged mode. If you connect to it you get an IP address assigned by the DHCP server on the SMC.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
172.17.2.3 is using port 7014
172.17.2.5 is using port 7013
With that configuration it should work. That is of course after I get the ISP involved and get them to change the modem to bridged mode.
I will reply as soon as that is done.
172.17.2.5 is using port 7013
With that configuration it should work. That is of course after I get the ISP involved and get them to change the modem to bridged mode.
I will reply as soon as that is done.
ASKER
I'm still waiting for my ISP to get back in touch with me. Since we have more than one static IP address is there any problem with placing the modem in bridged mode?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Okay the modem has been placed in bridged mode, but I am still unable to access anything utilizing 99.88.77.150.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've created everything you asked but it is still not working. I can't communicate to anything on 99.88.77.150 from outside.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER