Re: RDP
- From: andy <andyn141@xxxxxxxxx>
- Date: Tue, 19 Feb 2008 14:01:07 -0800 (PST)
On Feb 19, 1:43 pm, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
andy <andyn...@xxxxxxxxx> wrote:
On Feb 19, 11:55 am, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
andy <andyn...@xxxxxxxxx> wrote:
On Feb 19, 10:41 am, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
andy <andyn...@xxxxxxxxx> wrote:
Hello,
I'm running a sbs2003 domain. I have one remote worker who dials
into the server through sbs vpn and attempts to connect to his
desktop through rdp. It has been working fine for 8 months, and
now all of a sudden it has quit working. He can connect to the
vpn and gets and IP address but cannot connect to his desktop.
Can he ping it?
He can however, RDP to the
server.
I should certainly hope he can't log into it!
I did have terminal server lic installed, but I have since
uninstalled it. Any ideas as to why he can connect to the server
but not his desktop? As I said, it has been working up until
today. He can ping the server, but he can't ping his desktop.
Just kind of strange. Any ideas on this issue would be a great
help!
On the network, can you RDP to his desktop from your own?
Just out of curiosity, why aren't you using RWW for this?
Andy
LOL.....No, I don't let him access the server, I just wanted him to
see if it would pull up the login screen and it did. I can RDP from
my PC to his and that was one reason I thought it had something to
do with terminal lic.....
So you can, or cannot, just use the straight RDP client on your
workstation to access his on the LAN?
Also, do you know whether he can ping his PC when he has the VPN
tunnel established - by IP, and by name?
RWW, well when I use it, this is what I get :
The Client could not establis a connection to the remote computer.
The most likely causes for this error are:
1 Remote connections might not be enabled at the remote computer
2 The Maximum number of connections might be exceeded at the remote
computer.
3 A network error might have occured while establishing a connection
4 The RWW designated port might be blocked by a firewall
Its very possible that its the firewall, but I don't really want to
have to open ports if i don't have to. All I know is that the
current setup was working, and then all of a sudden it quit....
Check out the firewall on his PC - in fact, stop the underlying
Windows Firewall service entirely to test.
From my pc in the Lan, I can access his PC in the Lan, which is the
one he is trying to get to. When he is connected to the VPN tunnel, he
gets an IP address from the LAN and he can Ping the DC, however he
cannot ping the workstation on which he is trying to access (the same
one I CAN access internally)
Not even by IP address? What if the firewall is disabled entirely (stop the
service)?
This clearly points to the problem. Do you use ISA?
I don't use VPN for much. I suggest you see what happens when he uses RWW.
I figured out the problem. I was running trend micro's firewall on the
DC and that was blocking the RDP connection to go through. Once I
disabled that firewall, everything starting working perfectly. I just
don't understand what it was that all of a sudden made it stop
working, unless there was an update of some sort....
.
- Follow-Ups:
- Re: RDP
- From: Lanwench [MVP - Exchange]
- Re: RDP
- References:
- Prev by Date: RWW blocked to clients
- Next by Date: Re: Backup media (was: What backup software do you use and why?)
- Previous by thread: Re: RDP
- Next by thread: Re: RDP
- Index(es):
Relevant Pages
|
