![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I am trying to connect to my Vista Ultimate 32 machine from an XP Professional machine. I can't get a connection or even an attempt at a connection. Here is what I've tried so far. - I turned off the Windows firewall. - I am connecting from another computer inside my network. - I have tried both the (less secure) and (more secure) options in the Remote desktop area. - I have tried to telnet to my machine to port 3389 and it fails to connect. - I can ping the machine, see shared directories and connect to remote management. - I have turned on all services having to do with remote access and terminal services. So just clarify, it isn't a router issue, I am just trying to connect from one machine to another inside my network. Once I get that working, I will setup the router. I have been searching around for a while trying to find the answer to this problem. I have seen a hundred posts related to this topic but they all seem to end to at "try to telnet to port 3389" with no further responses. Any help would be greatly apprecaited. It seems like this is a fairly common vista problem so it would be great to find an answer. -- joebean |
|
|||
|
Well if you cant telnet 3389 it means something still blocking access to
that port, most likely another security sofware with integrated firewall is installed (or not correctly uninstalled). And yes it cant be a router issue as if i understand good both computer on lan and router only shaping wan-lan traffic. Csaba joebean write: I am trying to connect to my Vista Ultimate 32 machine from an XP Professional machine. I can't get a connection or even an attempt at a connection. Here is what I've tried so far. - I turned off the Windows firewall. - I am connecting from another computer inside my network. - I have tried both the (less secure) and (more secure) options in the Remote desktop area. - I have tried to telnet to my machine to port 3389 and it fails to connect. - I can ping the machine, see shared directories and connect to remote management. - I have turned on all services having to do with remote access and terminal services. So just clarify, it isn't a router issue, I am just trying to connect from one machine to another inside my network. Once I get that working, I will setup the router. I have been searching around for a while trying to find the answer to this problem. I have seen a hundred posts related to this topic but they all seem to end to at "try to telnet to port 3389" with no further responses. Any help would be greatly apprecaited. It seems like this is a fairly common vista problem so it would be great to find an answer. |
|
|||
|
By process of elimination, have your tried to connect from your Vista machine
to your XP Pro machine? If not, try that and let us know the results. Also, on your Vista machine, use the Command Prompt and type 'netstat -a' to view what ports are listening. "joebean" wrote: I am trying to connect to my Vista Ultimate 32 machine from an XP Professional machine. I can't get a connection or even an attempt at a connection. Here is what I've tried so far. - I turned off the Windows firewall. - I am connecting from another computer inside my network. - I have tried both the (less secure) and (more secure) options in the Remote desktop area. - I have tried to telnet to my machine to port 3389 and it fails to connect. - I can ping the machine, see shared directories and connect to remote management. - I have turned on all services having to do with remote access and terminal services. So just clarify, it isn't a router issue, I am just trying to connect from one machine to another inside my network. Once I get that working, I will setup the router. I have been searching around for a while trying to find the answer to this problem. I have seen a hundred posts related to this topic but they all seem to end to at "try to telnet to port 3389" with no further responses. Any help would be greatly apprecaited. It seems like this is a fairly common vista problem so it would be great to find an answer. -- joebean |
|
|||
|
Thanks for responding. Yes, I can connect to my xp pro machine from vista. I also can connect to a virtual machine running vista on the same computer from anywhere on the network. I am sure that there are no other firewalls running on my system. I have also ran Netstat -a and do not see port 3389 listed. Do you know the name of the process for Remote Desktop or is it listed as svchost.exe? -- joebean |
|
|||
|
On my Vista Ultimate box there are three that are pertinent. Here they are
along with the current state. Terminal Services - Started Terminal Services Configuration - Manual Terminal Services UserMode Port Redirector - Manual As an admin user run "services.msc" from the "Start - Run" command line. Check dependencies also for each service. -- Al Jarvi (MS-MVP Windows - Desktop User Experience) 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... How to ask a question http://support.microsoft.com/KB/555375 "joebean" wrote in message ... Thanks for responding. Yes, I can connect to my xp pro machine from vista. I also can connect to a virtual machine running vista on the same computer from anywhere on the network. I am sure that there are no other firewalls running on my system. I have also ran Netstat -a and do not see port 3389 listed. Do you know the name of the process for Remote Desktop or is it listed as svchost.exe? -- joebean |
|
|||
|
My services are setup identically to yours however, I do not see any dependencies listed for any of them. 'Sooner Al [MVP Wrote: ;731341']On my Vista Ultimate box there are three that are pertinent. Here they are along with the current state. Terminal Services - Started Terminal Services Configuration - Manual Terminal Services UserMode Port Redirector - Manual As an admin user run "services.msc" from the "Start - Run" command line. Check dependencies also for each service. -- -- joebean |
|
|||
|
One other thing. I am able to connect to my Vista Ultimate machine with Remote Assistance which I believe uses the same port 3389 however when I run netstat -a I still do not see anything connected to port 3389. I do see something listed as ms-wbt-server -- joebean |
|
|||
|
I finally found a temporary work around to the problem thanks to another post ('Terminal Services Failure - Windows Vista All' (http://www.techtalkz.com/windows-vis...-failure.html)) which stated "After hours of messing around with procmon, I fixed this problem on my machine. I discovered I was getting Access Denied in the registry for the svchost.exe that contained the terminal service, of course running as user "Network Service." This was very widespread (many different keys in HKCR and HKLM\Software), and my registry permissions matched a working machine. So, I fixed it by adding "Network Service" to the "Administrators" group. (Yes, bad.) Here is the command: net localgroup "Administrators" "NT Authority\Network Service" /add I had a different problem earlier this month where adding "Local Service" to the Adminstrators group was the fix. I found the method in this article: I can only assume the problems are related. Now I've totally undermined the sercurity of my system by adding these service accounts to the Administrators group, but I could find no other fix... (They are not designed to be in that group per ) If anyone has any other suggestions, I'm open to them. This seemed to stem from one of these patches, because Terminal Services ceased to function after the reboot:" -- joebean |
| Thread Tools | |
| Display Modes | |
|
|