Problem in connecting a RED10 (Rev 2) to our ASG220 (firmware: 8.304).
I've configured the RED using the RED Management->[Server] Deployment Helper. I've made sure that our ASG Hostname is reachable publicly as well as selecting the deployment of Standard: ASG controls remote network ... I've used the RED inerface IPv4 of: 10.20.0.1 (/24 255.255.255.0).
The device, associated interface, and network security entries are automatically made (without warnings and/or errors). I then plug the RED10 into one of my network ports (on the corporate network). It's WAN light blinks and then it cycles through the System, Router, Inernet, and Tunnel lights. All are solid green except for the Tunnel light. The tunnel light blinks for about a minute then the whole cycle begins over again. I've allowed this to cycle for the entire weekend and it hasn't connected.
I did have it working, but I used a ASG hostname that our ASG consultant said I shouldn't have. He asked that I get the real name accessible from outside our intranet and it should boot up just fine. He modified the configuration to have the new ASG hostname and rebooted the device (unplugged power and plugged back in). He did this last Wednesday, and I haven't gotten it to work yet).
Am I missing something obvious? I called Sophos support and had them reset the device and give me a new unlock code. I've also tried using the REDAlert.exe application. That application found the device on the network (had the correct MAC address listed) and gave the following information:
Resolved red.astaro.com to: red-prov-us.astaro.com (184.72.39.13)
Connected to Internet.
UNABLE TO CONNECT TO PROVISIONING SERVER
Resolved host: asg220a.pcink.com (23.x.40.100)
Connected to RED service on host (port 3400)
I'm assuming that this means that the configuration I've created exists on the astaro provisioning server and that our ASG is reachable from outside our network and that the RED service can have devices attached to it successfully. So why can't the RED device I've setup connect? Is it having trouble connecting to the provisioning server to download its configuration?
Any ideas and help are greatly appreciated. I'd like to be able to move on to getting a polycom phone working from a remote office ASAP. Thank you.
- Todd
I've configured the RED using the RED Management->[Server] Deployment Helper. I've made sure that our ASG Hostname is reachable publicly as well as selecting the deployment of Standard: ASG controls remote network ... I've used the RED inerface IPv4 of: 10.20.0.1 (/24 255.255.255.0).
The device, associated interface, and network security entries are automatically made (without warnings and/or errors). I then plug the RED10 into one of my network ports (on the corporate network). It's WAN light blinks and then it cycles through the System, Router, Inernet, and Tunnel lights. All are solid green except for the Tunnel light. The tunnel light blinks for about a minute then the whole cycle begins over again. I've allowed this to cycle for the entire weekend and it hasn't connected.
I did have it working, but I used a ASG hostname that our ASG consultant said I shouldn't have. He asked that I get the real name accessible from outside our intranet and it should boot up just fine. He modified the configuration to have the new ASG hostname and rebooted the device (unplugged power and plugged back in). He did this last Wednesday, and I haven't gotten it to work yet).
Am I missing something obvious? I called Sophos support and had them reset the device and give me a new unlock code. I've also tried using the REDAlert.exe application. That application found the device on the network (had the correct MAC address listed) and gave the following information:
Resolved red.astaro.com to: red-prov-us.astaro.com (184.72.39.13)
Connected to Internet.
UNABLE TO CONNECT TO PROVISIONING SERVER
Resolved host: asg220a.pcink.com (23.x.40.100)
Connected to RED service on host (port 3400)
I'm assuming that this means that the configuration I've created exists on the astaro provisioning server and that our ASG is reachable from outside our network and that the RED service can have devices attached to it successfully. So why can't the RED device I've setup connect? Is it having trouble connecting to the provisioning server to download its configuration?
Any ideas and help are greatly appreciated. I'd like to be able to move on to getting a polycom phone working from a remote office ASAP. Thank you.
- Todd