I had an Optiplex 330 that logged this error message under the “System” Event log. When you tried to connect to it via remote desktop, it would attempt to connect for about a half second and then the “connect” botton would be available again.
The fix? Going here: Display Properties –> Settings –> Advanced –> Troubleshoot, and turning off “Hardware acceleration”.
Don’t ask me… Some conflict with rdp.dll and the ATI video driver I suppose. I am also testing updating the video card driver as well.
First let me say that I was impressed with Linksys device. Nice little box for under $150.
I had some issues when I was deploying the QuickVPN client. The QuickVPN client allows you to connect from behind other Natting firewalls or other public networks, back to your “corporate” network. It is a piece of software that can be found at: http://www.linksys.com/servlet/Satellite?c=L_CASupport_C2&childpagename=US%2FLayout&cid=1169671133867&pagename=Linksys%2FCommon%2FVisitorWrapper&lid=3386724130B176&displaypage=nodata#versiondetail. When I tried to connect the QuickVPN, I would get an error message saying “The remote gateway is not responding, would you like to wait.” If you waited, it would do the same thing. If you check the log at C:\Program Files\Linksys\Linksys QuickVPN\log.txt, you see that it is failing to ping the remote gateway’s internal IP address (not the WAN ip).
The solution? Go to the Linksys’ website and download the latest firmware update – 1.2.11 as of this writing. That fixed it for me!
All the best of remote computing to you,
Luke
EDIT
It seems like you have to specify a private subnet in the 10.x.x.x range on the Linksys RVS4000. I had assigned 192.168.15.1 to the router, and I was connecting from clients that had a local IP of 192.168.1.X or 192.168.0.X. The QuickVPN seemed to work find on the 0.X networks, but on the 1.X networks I got a popup that said that it couldn’t connect. Changing the local subnet of the RVS4000 to 10.0.0.1 fixed all those problems….
Don’t ask me why it happened, but here’s the fix for some of those frustrations:
…Now you should be back in touch with your voicemail!
Excellent forum topic – helped me out a lot:
http://www.trixbox.org/forums/vendor-moderated-forums/sangoma/crackle-line
…Or not so happy.
After spending WAY too long trying to get my sip phones to register on a remote Trixbox, I figured out that the problem was due to my local Netopia router/modem from ATT messing with my SIP traffic. Here is the solution:
Telnet to your Netopia and:
The setting is not in the web gui. You have to telnet into the
router, then type. Each line is a new command.
configure
set ip sip-passthrough off
save
exit
Restart
On the Netopia 4622xlt
Telnet into the device
Use the arrow keys to highlight ‘quick menu’ and press “ctrl-n”
That brings you to the console.
type:
ip nat alg sip enable no
save
exit
restart
That info came courtesy of the following website: http://www.junctionnetworks.com/knowledgebase/onsip/devices/router-configuration/netopia