Question : Can't connect through router to Terminal Server

This one, I can't figure out.  I have a Win2K Server running Terminal Services. Connected to the outside w/a Netopia R-7100-C  DSL router.  Terminal svc works fine internally for several users.  When trying to come in from the outside, however, I get "The client could not connect to the server.  The server may be too busy. Please try connecting later."  From what I've been told, they used to connect from externally also.  After a lightning strike, the router was replaced several months ago, and since then external connections have not worked.  I've opened port 3389 in this router.   Netopia support even telneted in also & said it looks to be configured fine for the port forward.  Both server & router have been restarted.  If I run a port scan on the router from the outside, it doesn't show port 3389 as being open.  Is there any additional port that needs to be open to initiate the communication through 3389??  Also, as a side note (and possibly a related issue), I can telnet into the router through its external IP, however from the LAN side, I cannot ping its external IP.  It times out.  I can ping it from outside of the LAN, however.  I don't know if I'm missing something here that's right under my nose, or if it's a more complex issue.

Answer : Can't connect through router to Terminal Server

The ping is not suprising, it's probably being blocked by the firewall.

I'm not sure if your configuring the rule in the right place.
I'm looking at http://www.netopia.com/equipment/pdf/manuals/r7100/sdslref.pdf on page 75 it talks about Filter Sets.

Try removing the previous "Add Server" rule and add a filter rule that looks like this:
source     destination                Proto      Src.Port     D.port       On?       Fwd
0.0.0.0          TCP            0          =3389       Yes         Yes

Source/Destination Port compare = No compare

You could also use the example FTP rule they are adding on page 170. Just change the port to 3389.