This unit was installed in the fall of 2013 for a client and right away we started having problems with the remote services including VPNs, port forwarding, and remote management. We got ticket opened and the result was we recieved and implemented a beta firmware and that mitigated the issues to some extent (with the exception of remote management) but enough that the client was happy.
As part of normal maintenance we recently implemented the latest firmware issued in December (1.1.6) and it seems we have taken us a step backwards. The unit needs to be manually restarted every two to three days for the remote access features to work as expected. I would thought the fixes in the Beta we got would have been carried through to the final release in December.
Has anyone else had this occur and other than "downgrading" back to the Beta, does anyone have a suggestion (other than replace with another unit)?
Email the escalation engineer that provided the beta firmware link to you and let them know about the issues that you are experiencing with the public release. They should be able to tell you if there is another beta available or if the issue should be fixed.
Hi every one!!!When you are configuring a remote VPN connection, there
are some steps that are lost on the path. Here you can see those steps.
A) In your Cisco device: 1. Ensure you don´t have any rule denying the
traffic between the device and the remote...
** Update **These and a number of other issues have been addressed in
SRP520 MR3. Please see https://supportforums.cisco.com/docs/DOC-13853
for details on how to access this code.There have been a number of
reports of the SRP500 becoming unresponsive afte...
STANDARDSOURCECOMMENTSEthernet RJ-45 connector pin number12345678IEEE
802.3afusing data pairsRXDC+RXDC+TXDC-sparespareTXDC-sparespareIndustry
Standard for Embedded POE(used by Cisco Catalyst Switches)IEEE
802.3afusing spare pairs RXRXTXDC+DC+TXDC-DC-Indus...