Question

Locked

Unable to remote desktop to my server

By rohanverma ·
Hello,

I am trying to connect to my home server (Windows Server 2003) from my home laptop. Both are on my home network using a Linksys WRT54G router. A few days back we had power outage and on restarting the server I got "IP conflict" error. Since than I have not been able to remote desktop into my server from my home laptop and work laptop.

Both server and laptop are connected to the internet. I have checked the firewall, port 3389 is open for server ip but still no luck. Please see below my ipconfig/all data, can anyone help me locate the problem?

I am not very tech savvy thus asking for help.

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

Windows IP Configuration

Host Name . . . . . . . . . . . . : vatodbs01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server Adapter
Physical Address. . . . . . . . . : 00-02-B3-B7-94-CB

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter (1
0/100)
Physical Address. . . . . . . . . : 00-06-5B-8D-BF-3F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 64.71.255.198
Lease Obtained. . . . . . . . . . : Wednesday, February 23, 2011 7:15:22 PM
Lease Expires . . . . . . . . . . : Thursday, February 24, 2011 7:15:22 PM

C:\Documents and Settings\Administrator>

Thanks

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

To clarify

by robo_dev In reply to Unable to remote desktop ...

You have one Ethernet connection to your server, correct?

Are you using Windows Internet Connection sharing on the server? That could cause the IP address conflict.

From your home laptop:
- Can you ping the server IP address?
- Is the remote desktop service running on the server?
Look in the event log of the server to see if the service is crashing or failing to start

- What error, if any, are you getting on the home laptop when it tries to connect to the server?

Sorry to lecture here, but:

From a security perspective, there are tons of exploits and vulnerabilities for RDP (remote desktop protocol). I would not recommend using it unless you really had to, and even then there would be a long checklist of required server patching/hardening as well as some very aggressive and active monitoring. Seriously, opening port 3389 is like a big neon sign that says 'OPEN' for hackers. On my firewall I see at least a couple of dozen port 3389 probes a day. At the VERY least, change to a different port; that's 'security through obscurity' but it's better than nothing. That being said, the cause of your failure could be that your server has been hacked.

While an IP address conflict on a simple small network can happen when a Wireless device goes to standby or hibernate, it would also be a sign that something is not kosher in the server, e.g. a rootkit of some sort.

End of today's lecture on security

Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums