Cannot remote into some XP Pro workstations

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have just installed a workstation with XP Pro and after activating Remote
Desktop with myself and my boss the only people with usage rights, I find I
cannot remote into this machine. The downloads are up to date.

Why can't I remote into it?
 
Can you telnet port 3389?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have just installed a workstation with XP Pro and after activating Remote
Desktop with myself and my boss the only people with usage rights, I find I
cannot remote into this machine. The downloads are up to date.

Why can't I remote into it?
 
Carl Gross said:
I have just installed a workstation with XP Pro and after activating Remote
Desktop with myself and my boss the only people with usage rights, I find
I
cannot remote into this machine. The downloads are up to date.

Why can't I remote into it?
Click to expand...

This page may be of help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
No I can't. (Interesting. I've never tried this before. I tried it on
machines I can remote into and I get what appears to be a successful telnet
session. I don't know what to do with it once I'm in, but it's different from
the results I get with the machines I'm having trouble with.)
 
Another funny thing. When I ping the computer name of the sick machine, I
get the IP address of a different machine.

eg. if mac1 is the sick one I get the IP address 192.168.100.111 but the
real address is 192.168.100.123 (i went to the machine and typed ipconfig
/all)

Could this be a DNS problem and would that effect Remote Desktop? If so,
what do I do?
 
I tried a "netstat -a" and it said port 3389 is listening but when I went to
the web site "www.canyouseeme.org" and asked it to check port 3389 it said
3389 is not open.

I pinged the sick machine and it gave me the IP address of another machine.
ie. the sick machine (Mac1) answered the ping with 192.168.100.111, but when
I went to the machine it had an IP address of 192.168.100.123.

Could this be a DNS issue? If so, how do I fix it?
 
Carl Gross said:
I tried a "netstat -a" and it said port 3389 is listening but when I went
to
the web site "www.canyouseeme.org" and asked it to check port 3389 it said
3389 is not open.

I pinged the sick machine and it gave me the IP address of another
machine.
ie. the sick machine (Mac1) answered the ping with 192.168.100.111, but
when
I went to the machine it had an IP address of 192.168.100.123.

Could this be a DNS issue? If so, how do I fix it?
Click to expand...
Are you using a static IP for the PC you want to remotely access/control
using Remote Desktop? You should simply because if you reboot a machine and
your not using a static IP then you may negate any port forwarding
configuration you have in your router.

http://www.portforward.com/networking/staticip.htm

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I have two machines that are having this trouble. One is set up statically
and one is set up dynamically. They both will not allow remote desktop.

By the way, what is HHCTRL.OCX? I'm getting a popup during reboot that its
conflicting memory location with user32.dll. The help screen said its
probably a rights issue, but changing the users rights to administrative
didn't work. I'm asking because I know I'll hear about it soon, so I wanted
to know what I can do to remedy it (ie. the help screen wasn't very helpful).
 
Carl Gross said:
I have two machines that are having this trouble. One is set up statically
and one is set up dynamically. They both will not allow remote desktop.

By the way, what is HHCTRL.OCX? I'm getting a popup during reboot that
its
conflicting memory location with user32.dll. The help screen said its
probably a rights issue, but changing the users rights to administrative
didn't work. I'm asking because I know I'll hear about it soon, so I
wanted
to know what I can do to remedy it (ie. the help screen wasn't very
helpful).
Click to expand...
http://search.live.com/results.aspx?q=HHCTRL.OCX&src=IE-SearchBox

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Something interesting, I had to restart the server and while it was still
restarting I was able to telnet into both machines that are having trouble.
DNS maybe? If so what do I do?
 
Something interesting. I recently had to restart the server and while it was
restarting I tried telnetting into the two effected machines and was
successful. Could it be a DNS problem?

If so, how do I fix it?
 
Carl Gross said:
Something interesting. I recently had to restart the server and while it
was
restarting I tried telnetting into the two effected machines and was
successful. Could it be a DNS problem?

If so, how do I fix it?
Click to expand...
What server? I think you need to describe the network in a bit more detail.
I thought you were trying to connect to one or two standalone desktop PCs
from another PC.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
You're right. I should have described the network environment first.

We have an SBS 2003 server with Exchange 2003 and SQL Server 2000. We are
currently in the process of switching our workstations from W2K SP4 to Win XP
Pro SP2. We use DHCP for our IP addresses and DNS. As the network admin,
though, I need to be able to remote into our workstations. I believe this
should be able to occur independent of our server, but this last note from me
probably proves me wrong.
 
Carl Gross said:
You're right. I should have described the network environment first.

We have an SBS 2003 server with Exchange 2003 and SQL Server 2000. We are
currently in the process of switching our workstations from W2K SP4 to Win
XP
Pro SP2. We use DHCP for our IP addresses and DNS. As the network admin,
though, I need to be able to remote into our workstations. I believe this
should be able to occur independent of our server, but this last note from
me
probably proves me wrong.
Click to expand...
Since this is a SBS and presumably also a domain environment then I suggest
you post to the SBS news group.

microsoft.public.windows.server.sbs

I only work in a small office/home office (SoHo) environment, ie. work
group. I will tell you that setting static IP addresses for the desktop
workstations will insure you actually connect to the workstation you want to
connect to.

http://www.portforward.com/networking/static-xp.htm

Sorry I can't be of more help...

Good luck...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Carl Gross said:
By the way, what is HHCTRL.OCX? I'm getting a popup during reboot that
its
conflicting memory location with user32.dll. The help screen said its
probably a rights issue, but changing the users rights to administrative
didn't work. I'm asking because I know I'll hear about it soon, so I
wanted
to know what I can do to remedy it (ie. the help screen wasn't very
helpful).
Click to expand...
I just ran across this courtesy of another MVP... It may help with the
HHCTRL.OCX issue...

http://support.microsoft.com/kb/935448

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Back
Top