Nokia IP 260, allowing a remote office having a direct connection
We have a Private WAN Frame Relay connecting all our office. We have the Nokia IP260 in the central head office (Nokia LAN IP Address 188.8.131.52). The local LAN users with in head office can comminicate directly to the IP260. However we will like to the remote offices (IP Address 184.108.40.206/24) to be able to access the IP 260. I have already added a static route in the Voyager, and allowed a rule within checkpoint for the IP range 192.100.105.x, but the remote office still dosen't have access. All help will be appreciated. thanks
Re: Nokia IP 260, allowing a remote office having a...
You should disable NAT between your local networks in the Checkpoint NAT policy (Create a NAT rule above all and put all your networks in the source and destination - as a group)the leave Original in the translation column.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Configure the 3COM to direct all incoming 3389/TCP traffic to 3389/TCP on the "private" IP-address (192.168.xx.yy) of your server.
Configure your server to "allow" Remote Desktop connections, and add the ID/password details that will be allowed to login to your server.
192.168.1.X is a local ip address ,, i trust that thhe vpn is in seperate places and is done with the wan ip over an internet connection?????
OK maybe the problem isnt on your side but the main office building,, when connecting , have someone looked for repeated attemps to connect by observing the fire wall,, if it appears to be blocked byu the firewall simply diasable any and try it out.. If it works then all you need to do is set the firewall correctly..
I was reading the ip address in your original post and those are local address,s are you certin the VPN is correct ???? did you use the correct STATIC IP ADDRESS ASSIGNED BY YOUR ISP??
There may be some problem in your net connection or problem in that ip.Check your connection again and then do ping for some familiar ip's like Google,Yahoo,and so on in cmd.If it works well,check with the IP you need.If it shows the same error again,then sure the problem is on the Ip.You can do ping in cmd by typing ping website name.You can also do ping test at Whoisxy.com .
This sounds like a route problem. This can happen if the settings to the WAN are correct. If you are using a dialup DSL router check to make sure that it is connecting to your ISP. Same for a cable modem. Once you have verified that it is connected properly then set your WLAN gateway to point to the WAN IP number. if you are using DHCP for IP addressing for your wireless devices make sure that the gateway address is set correct also. Check DNS settings sometimes the ISP's DNS servers are not setup correctly or are not stable try using googles free DNS numbers of 220.127.116.11 or 18.104.22.168
This is not directly possible to do with a TZ170 as the device will only allow configuration for 1 static or dynamic IP at a time for the WAN port. However this being the case, I suggest setting the SonicWALL up as a perimeter firewall and place devices that require the other public IPs form the additional IP range behind the TZ170. Basically the SonicWALL becomes the gateway for the other IPs needed as long as the range of the IP block is contiguous. This would involve using the 4 ports of the LAN on the back of the TZ170 to connect directly to the other devices or if it is more then 4 devices, using a switch connected to the LAN side of the SonicWALL to provide connectivity to the multiple devices behind it. Most TZ170 are licensed for 10 connections on the LAN side and if you require more then 10, additional licenses will need to be purchased. I would be careful pushing too much traffic through a TZ170 as it is designed for Small Business use and will quickly become overloaded with too much traffic causing high latency/traffic bottlenecks and in extreme cases connections being dropped. This is especially true for multiple VPNs.
If you're within a network and try connecting to computers on it with the WAN public IP, it simply won't work - you must use the network IP.
On an external Internet connection, it should connect fine to the public IP. If you have access to an external machine (remote desktop), or if you know of an FTP proxy, you can try it that way.
I also believe http://www.webftp.co.uk/ a web based FTP client would act as somewhat of a proxy, you could try that with the public IP and see how you go.