Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Accessing Remote PC
- Thread starter zib
- Start date
- Thread starter
- #3
What happens when they change? Has your ISP stated that they support this? Some ISP's do not allow RDP. You can try and trick them by using another port, but if your ISP has direct access to your modem/router, they can very easily configure your modem to only be a "one way" modem/router. Meaning, only information that a connection asks for will be answered, and won't allow outside connections to "call the shots".
- Thread starter
- #6
Are either pc's behind a firewall? If they are then you need to enable 'Remote Destop' or 'Remote Assistance' as an exception. If they are not behind firewalls and they IP's that they get are external i.e. not 192.168.1.X then just run 'mstsc' from the run prompt and type in the remote address.
Alternatively you can use TightVNC which is free and has more features.
Alternatively you can use TightVNC which is free and has more features.
I am flabbergasted.
While I have seen it commonly done in the terms of contract that a server service is not allowed, I have yet to see or hear anything about an RDP connection being blocked by an ISP firewall.
Please, will tfg13 give us a listing of ISPs that implement this as policy or state this in their service contracts to the consumer or business?
And this statement by tfg13 is technicly limited to cable ISP services, and reflects paranoia and "black helicopters" type thinking. Please tfg13, give us an example of where an ISP went and reconfigured a site modem to block RDP traffic:
These are outrageous claims.
While I have seen it commonly done in the terms of contract that a server service is not allowed, I have yet to see or hear anything about an RDP connection being blocked by an ISP firewall.
Please, will tfg13 give us a listing of ISPs that implement this as policy or state this in their service contracts to the consumer or business?
And this statement by tfg13 is technicly limited to cable ISP services, and reflects paranoia and "black helicopters" type thinking. Please tfg13, give us an example of where an ISP went and reconfigured a site modem to block RDP traffic:
These are outrageous claims.
I've never heard of ISPs blocking RDP connections per se, but I have heard of a number of instances where ISPs are giving users non-routable IP addresses to save their public IP space. This would certainly throw a spanner in the works!
Ed Metcalfe.
Please do not feed the trolls.....
Ed Metcalfe.
Please do not feed the trolls.....
Try doing it with a Time Warner roadrunner "owned" router. Had one at a business, and in the contract it specifically stated that you won't be able to utilize any "inbound" connections. I no longer work at that business, so I won't be able to get the wording verbatim, but it indeed did hamper Remote connections to this network. If you utilize the modem/router that is given to you by the ISP, then you are under their rules, and they have to authority to reconfigure the modem/router as they see fit. I'm not saying that it happens with all ISP's, but it does happen. Ever heard of a user getting throttled for bandwidth consumption? How do you think they were throttled?
To say that I am paranoid, bcastner, is something you should be ashamed of. I would think that with the amount of posts, and answers I've given on this site would hamper your statement, but I guess not. No where in my statement did I say "Big Brother" is watching. Being a US federal employee, I won't acknowledge those statements, and I won't deny those statements.
To say that I am paranoid, bcastner, is something you should be ashamed of. I would think that with the amount of posts, and answers I've given on this site would hamper your statement, but I guess not. No where in my statement did I say "Big Brother" is watching. Being a US federal employee, I won't acknowledge those statements, and I won't deny those statements.
John Lewis
Programmer
There was a time, long long ago, when RoadRunner (and the other cable providers) blocked traffic on common server ports. These restrictions were more a matter of neccessity than a desire of the cable operators to limit the functionality of their networks. Upstream and downstream traffic are handled differently on a cable network. Under early standards, it was assumed that upstream traffic would be significantly less in terms of the amount of data being moved and that upstream traffic would be rather sporadic or bursty. Placing a server on a cable connection would not fall into that scenerio, and as such would cause upstream loads that the system was not capable of dealing with and still maintain reasonable service to other subscirbers.
Cable infrastucture and technology has changed and the RoadRunner policy has changed accordingly. Everything is open now, with a few minor exceptions. Also, RoadRunner now allows users to supply their own cable modem, so you are not stuck with what they supply, although I can't think of any good reason someone would want to buy additional hardware at this point. None of the cable systems I come in contact with today have unreasonable blocks in place, although there certainly may still be some that do.
On the point of throttling bandwidth and blocking ports, it is worth noting that these are two completely different issues. Throttling takes place at layer 2 and is not an IP function in this case, and as such has very little relation to the idea of blocking ports. When the port filtering was in place, it did not happen at the modem level, but somewhere within the IP network of the cable provider.
At this point, it really does not make much sense for any ISP to attempt to block ports. Most of the broadband routers available today allow for a port to be forwarded to a different port on an internal machine. Several dynamic DNS services offer port redirection services, so it becomes very easy to circumvent these efforts.
One last point before I finish this rant. Broadband ISPs certainly do block some ports, but this is a good thing. 137-139 and 445 are commonly blocked to dissallow simple file sharing over the internet and reduce broadcast traffic on the local IP network. This is realatively recent for RoadRunner, and prior to the port blocks being put in place it was usually possible to find 8-10 computers broadcasting to the local subnet, usually with drives shared without passwords. Sometimes it is necessary to protect people from themselves.
Cable infrastucture and technology has changed and the RoadRunner policy has changed accordingly. Everything is open now, with a few minor exceptions. Also, RoadRunner now allows users to supply their own cable modem, so you are not stuck with what they supply, although I can't think of any good reason someone would want to buy additional hardware at this point. None of the cable systems I come in contact with today have unreasonable blocks in place, although there certainly may still be some that do.
On the point of throttling bandwidth and blocking ports, it is worth noting that these are two completely different issues. Throttling takes place at layer 2 and is not an IP function in this case, and as such has very little relation to the idea of blocking ports. When the port filtering was in place, it did not happen at the modem level, but somewhere within the IP network of the cable provider.
At this point, it really does not make much sense for any ISP to attempt to block ports. Most of the broadband routers available today allow for a port to be forwarded to a different port on an internal machine. Several dynamic DNS services offer port redirection services, so it becomes very easy to circumvent these efforts.
One last point before I finish this rant. Broadband ISPs certainly do block some ports, but this is a good thing. 137-139 and 445 are commonly blocked to dissallow simple file sharing over the internet and reduce broadcast traffic on the local IP network. This is realatively recent for RoadRunner, and prior to the port blocks being put in place it was usually possible to find 8-10 computers broadcasting to the local subnet, usually with drives shared without passwords. Sometimes it is necessary to protect people from themselves.
- Status
Similar threads
- Locked
- Question