RDS tunnels the rdp protocol through SSL/443 so it shouldn't be going over 3389 directly.
Port 3389 (RDP) to go through another companys proxy/firewall....
- Thread starter R.O.S.S.I
- Start date
RDS tunnels the rdp protocol through SSL/443 so it shouldn't be going over 3389 directly.
Well this is exactly what I thought, I thought it sent it over SSL/443 for this exact reason?!
Anyone know how I can check this out? His exact words are....
Really stuck with what to do! Its doing my bloody head in!
Soldato
- Joined
- 6 Sep 2008
- Posts
- 3,974
- Location
- By the sea, West Sussex
Ah my mistake, it's SSL up to the gateway but it's RDP from the gateway. Things have changed a little since I last used it!
The 2 things I would be asking myself in this situation....
1) Does it work from elsewhere, if so it's a problem the other end.
2) Can you verify he's doing everything right his end - how is he confirming it's going out on 3389? Can you get a get a packet capture from a client his end??
The 2 things I would be asking myself in this situation....
1) Does it work from elsewhere, if so it's a problem the other end.
2) Can you verify he's doing everything right his end - how is he confirming it's going out on 3389? Can you get a get a packet capture from a client his end??
The whole system works fine as I can log in from home fine using it. I've had colleagues try from their homes too and had a friend at a local business try it just so I could make sure and the whole setup runs as it should.
Its not an issue with the system working or not. Its how it is making the connection.
I've just took what he says at face value really as its pretty hard to mess up logging on through our web access gateway. I told him he should go to our web gateway address and pop in the specified username and pass to access.
So should I be asking him for some confirmation that shows it is going out on 3389?
Its not an issue with the system working or not. Its how it is making the connection.
I've just took what he says at face value really as its pretty hard to mess up logging on through our web access gateway. I told him he should go to our web gateway address and pop in the specified username and pass to access.
So should I be asking him for some confirmation that shows it is going out on 3389?
Soldato
- Joined
- 6 Sep 2008
- Posts
- 3,974
- Location
- By the sea, West Sussex
Well the point I was making is that if no-one else could connect it may have been a system misconfiguration, but you've clearly shown that not to be the case so the problem HAS to be at their end.
I'd be asking for a packet capture, not only for verification to see what he is saying is correct, but to see if it sheds any light on the issue.
Have you tried asking them for a Teamviewer / Logmein type session so you can see the problem for yourself? The only reason I ask is that I worked on a software integration project where the other companies helpdesk kept coming back to us with problem after problem during testing that we could not replicate....turns out they were not following the instructions we'd given them at all and were just doing things how they felt you'd like to do them :-/
I'd be asking for a packet capture, not only for verification to see what he is saying is correct, but to see if it sheds any light on the issue.
Have you tried asking them for a Teamviewer / Logmein type session so you can see the problem for yourself? The only reason I ask is that I worked on a software integration project where the other companies helpdesk kept coming back to us with problem after problem during testing that we could not replicate....turns out they were not following the instructions we'd given them at all and were just doing things how they felt you'd like to do them :-/
I think you mentioned above that you closed 3389 on your router and it stopped working, is this still the case?
Yeh think I did actually. When I take that port forward off i'm unable to make a successful connection through the RDWEB Access page, but I can still connect if I use MSTSC and select to use the RD WEB Gateway server instead.
I might get him to try connecting through mstsc.exe and specify our gateway server in there and see if that works.
Last edited: