I can't get a connection to it from outside my network I forwarded port 3389 to that machine on the network, but no one is capable of connection from outside my network
From outside the network, can you open a command prompt and run 'telnet your_ip 3389'? You should get a blank box. What are the people outside your network using to connect? What error do they get?
Connection failed when trying to telnet, and when trying to Remote COnnect in it says that it can't create a connection and that it may be busy or the computer isn't running a server. I know it has something to do with my crappy linksys router, but I have all the correct ports setup in UPnP on the router page.
Anyone out there with a BEFSR41 with RDP forwarding working correctly that can help out? I would hate to see you get a new router if you don't need one.
Alot of apps have had problems with forwarding on my router, I've just either always found ways around, or given up on that program but I can't deal with it in this situation. Any reccomendations?
Sounds like you need to take a step back and examine your router setup. I have 3 websites, exchange server with OWA running with SSL and VPN running through one of those crappy gay a** little blue boxes. It just happens to be the exact model you are using and it has been running perfectly for years. Looks like you need to brush up on your networking skills before you start calling things crappy!!
I don't pretend to know WTF I'm doing, but i can follow directions, I have a jpeg of my router settings, give me an email addy and I'll shoot you an email and you can tell me what's wrong with it.
I've used TS under W2k Server for over three years. I *tried* implementing a 2k3 server with it and had miserable results. Scratched it and went back to running W2K TS.
You can buy a Poweredge server for $500. A licensed copy of W2K server with 25 CAL's for under $500 on Ebay. TS access CAL's are about $65 a pop. Or at least that was what I was buying them for from CDW.
So for a little over $1700 you can get set up. All in all, that's pretty reasonable. Once you get a TS up and running your end users won't be able to live without it.
2000 terminal servers can access a built in pool of licenses on the license server. This means that you dont need to purchase TS CALs for XP Pro and 2000 Pro clients that connect to a 2000 terminal server. You'll hear a lot of people say that XP and 2000 have a built in TS license when connecting to a 2000 TS, but this isn't true.
Just to let you know, found out the router problem, ISP has one public IP and we're all private IP's within the network, and they don't forward ports to anyone... So it was on the ISP's side not mine, $10 a month more for an external static IP, but it's all good.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.