Recent content by littlebluedevil

Then I would say that your company might be filtering the port based on http packet headers. If you are a sys admin, you can always change that ;)

I know this is a stupid question, but I have to ask ... when you are trying to connect, are you specifying :8080 after the ip address?

Thanks for your reply. Can I ask why you switched? LBD

Hello all, I'm doing a bit of research and I would like to know people's opinion of Winternal's Defrag manager 2.5 and Executive Software's Diskkeeper 8. Opinions good and bad are welcome. Also, I am going to be running some tests and I would like to know the best way to test my I/O performance...

It was still listening on 3389, so I did a system restore, reset the port to 8080 and it worked. Thanks for all your help. LBD

I'll give it a shot. Thanks,

Thank you for your reply, but I already do that. The problem is that I've set it so the terminal services are listening on port 8080, but when I try to connect to 192.168.1.103:8080 I get a connection error. When I connect to 192.168.1.103, it works just fine. However, I NEED it to be...

I'm using the xp terminal services client to connect, not a web client. I have this working on another system using another port. I open up the registry and it says that its listening on 8080, but when I connect, its connecting to 3389. Has anyone experienced this?

Hello, I have a similiar issue. I changed the port that the terminal service listens on to 8080 and opened up the appropriate port on my firewall. However, I cannot connect to it on port 8080, only the default port. So I can connect no problem, its just not listening on the port I specified...