Computing.Net > Forums > Windows Server 2003 > Cannot Login Via remote desktop

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Cannot Login Via remote desktop

Reply to Message Icon

Name: drkwtsn
Date: February 3, 2004 at 18:25:29 Pacific
OS: Windows 2003 Server
CPU/Ram: Athlon / 512
Comment:

I cannot log in remotely via remote desktop... When i try to connect it says the clien could not connect to the remote computer.... This is on a lan.. If i try to connect via remotedesktop to the windows 2003 server FROM the windows 2003 server (to see if the service is even running) it lets me connect.... any ideas of where to start?



Sponsored Link
Ads by Google

Response Number 1
Name: blin
Date: February 3, 2004 at 19:29:14 Pacific
Reply:

can you ping the server? or post the results of computers' ipconfig /all.

For more tips or information, go to http://www.ms-mvps.com

Robert, MS-MVP, MCSE and CNE
Networking, Internet, routing & VPN Support, Tips and FAQs on
http://www.ms-mvps.com


0

Response Number 2
Name: drkwtsn
Date: February 3, 2004 at 21:03:38 Pacific
Reply:

yes i can ping the server
here is ipconfig /all

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : galaxyserver
Primary Dns Suffix . . . . . . . : GalaxyPC.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : GalaxyPC.local
owngsm01.md.comcast.net

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . : owngsm01.md.comcast.net
Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Adapter
Physical Address. . . . . . . . . : 00-E0-18-BB-59-26
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.54.80.5
68.54.80.6
Primary WINS Server . . . . . . . : 192.168.1.100
Lease Obtained. . . . . . . . . . : Tuesday, February 03, 2004 1:56:48 PM
Lease Expires . . . . . . . . . . : Wednesday, February 04, 2004 1:56:48 PM


0

Response Number 3
Name: Antero
Date: February 4, 2004 at 00:40:26 Pacific
Reply:

Terminal Server is installed? Computer is member in domain/computers?


0

Response Number 4
Name: drkwtsn
Date: February 4, 2004 at 06:30:28 Pacific
Reply:

After doing some checking, terminal server licensing was not installed... I installed that but i do not have a license pack... I thought I could let people login via remote desktop with SBS Premium??? I'm lost :(


0

Response Number 5
Name: Glen
Date: February 4, 2004 at 10:04:32 Pacific
Reply:

Antero, TS is installed by default. You don't need to install it. You also don't need to install TS licensing. Take it off.

You need to enable the Remote Desktop to connect to it.

Right click on My Computer, select the Remote Tab, check the box for Allow USers To Connect Remotely...

Good luck.


0

Related Posts

See More



Response Number 6
Name: drkwtsn
Date: February 4, 2004 at 12:59:38 Pacific
Reply:

yeah that is enabled


0

Response Number 7
Name: Glen
Date: February 4, 2004 at 13:54:03 Pacific
Reply:

Why are you using WINS, and do you have a domain? I assume you don't have a domain based on your DNS information in your IP config. Have you tried to connect to the remote machine via IP address instead of name? If so, you have a DSN or name resolution problem.


0

Response Number 8
Name: jefro
Date: February 4, 2004 at 14:46:37 Pacific
Reply:

It should work locally on the server using that IP. It should work remotely using that IP. All that is needed is the remote destop being enabled and the user being part of remote desktop users.


0

Response Number 9
Name: jefro
Date: February 4, 2004 at 16:22:53 Pacific
Reply:

you might not have an updated version of rdp client? Use the CD or net to get newest version for your remote system. Also see about tsweb and be sure your know what ports have to be open for rdp.


0

Response Number 10
Name: drkwtsn
Date: February 4, 2004 at 17:19:03 Pacific
Reply:

i tried to get a new version of RDP on microsoft.com but when i tried to install it said it couldnt install because i already had a built in version.
How would I go about opening ports on my w2k3 machine?


0

Response Number 11
Name: jefro
Date: February 4, 2004 at 20:24:34 Pacific
Reply:

That was more if you had a router or firewall installed. Since you can access it from another 2003 we can suspect that it really works at the server. I was unsure of your topology, you might have another lan device in the way of the client. I used xp home to access my 2003 server. It took a while too. I know I did something that finally fixed it. I think I made it a trusted computer or something. Otherwise the XP home computer just wouldn't see the shares or ftp or rdp on the server even though the server could access the shares on the xp home. Seem like some permission or acl ,, darn, I can't remember what I read that led me to getting it fixed.


0

Response Number 12
Name: neoandmatrix
Date: February 7, 2004 at 15:01:05 Pacific
Reply:

Hello,

After create account for remote users,add a Remote Desktop Users*.account creates in Users but you cannot see in Users.Remote Desktop Users is in Builtin.

*(in Active Directory Users and Computers)


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Cannot Login Via remote desktop

cannot gain remote desktop access v www.computing.net/answers/windows-2003/cannot-gain-remote-desktop-access-v/3594.html

Remote Desktop Connection won't wor www.computing.net/answers/windows-2003/remote-desktop-connection-wont-wor/8188.html

remote desktop / audio www.computing.net/answers/windows-2003/remote-desktop-audio/339.html