Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Windows 2000 Server problems

Original Message
Name: Jrb599
Date: November 19, 2007 at 21:29:44 Pacific
Subject: Windows 2000 Server problems
OS: 2000 server
CPU/Ram: 2.0/512
Comment:
I've tested my my router and have port fowarding set up correctly, I know i have some problem set up with my Windows 2000 server wrong

When I connect to it outside of the router, I can't get in, but when I connect within the network, no problem. Any suggestions on a setting they might be wrong

69.134.148.31 is the ip address.

Also my internet provider blocks no ports



Report Offensive Message For Removal


Response Number 1
Name: Curt R
Date: November 20, 2007 at 09:30:14 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
If you're trying to connect with RDC (remote desktop control) then you need to forward port 3389 on your router/firewall to the IP address of the computer/server you wish to connect to.

I suggest you go back over your port forwarding on the router and double check you have the forward itself setup properly. Since you can connect fine from within the LAN, it's highly unlikely it's a problem with the server. The most likely suspect is the router.

Oh, one other thing to check, the built in Windows firewall on the server itself. If you have it enabled, it could be what's preventing you from connecting remotely (providing the port forward on your router is setup correctly). If that is the issue, you have two choices. Either disable the builtin firewall completely, or, create another port forward on it.


Report Offensive Follow Up For Removal

Response Number 2
Name: Jrb599
Date: November 20, 2007 at 12:42:33 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Added port fowarding to 3389

69.134.148.31:3389 won't let me in

how do I turn off the firewall


Report Offensive Follow Up For Removal

Response Number 3
Name: Curt R
Date: November 20, 2007 at 14:09:30 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
You don't need to add the port number at the end when connecting with RDC. Just the external IP of your connection will do.

If the builtin windows firewall is turned on, you can access it and turn it off via:

Control Panel >> Windows Firewall

If it is on, don't forget you can also open port 3389 on it as well to allow the traffic through.


Report Offensive Follow Up For Removal

Response Number 4
Name: Curt R
Date: November 20, 2007 at 14:10:25 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Oops, my bad, one thing I forgot. Open System Properties (in Control Panel) and click on the "Remote" tab. Ensure you have enabled Remote Desktop.

Report Offensive Follow Up For Removal

Response Number 5
Name: Jrb599
Date: November 20, 2007 at 15:39:03 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Windows 2000 Server doesn't have a firewall


Report Offensive Follow Up For Removal


Response Number 6
Name: Curt R
Date: November 20, 2007 at 15:48:49 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Oh yeah, that's right.....LOL. It has been a while since I looked at 2000.....

Report Offensive Follow Up For Removal

Response Number 7
Name: wanderer
Date: November 20, 2007 at 17:22:23 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Doesn't mean one didn't get installed! Should check anyway

Imagine the power if you knew how to internet search


Report Offensive Follow Up For Removal

Response Number 8
Name: Jrb599
Date: November 20, 2007 at 17:59:04 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
how do I check?

Report Offensive Follow Up For Removal

Response Number 9
Name: wanderer
Date: November 20, 2007 at 18:00:15 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Add/remove programs

Imagine the power if you knew how to internet search


Report Offensive Follow Up For Removal

Response Number 10
Name: Jrb599
Date: November 20, 2007 at 18:07:23 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
none
found

Report Offensive Follow Up For Removal

Response Number 11
Name: wanderer
Date: November 20, 2007 at 18:24:32 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Remote desktop engaged?

When you say "69.134.148.31:3389" are you trying to access via your lan? or are you going somewhere else for internet access and testing?

Did you try from a xp box and RDP without the port number on the end?

When you say "69.134.148.31" that is the ip of your ROUTER correct? DID you add that port number to your router and FORWARD it to your server?

What is the exact message you get when it fails?

Imagine the power if you knew how to internet search


Report Offensive Follow Up For Removal

Response Number 12
Name: Jrb599
Date: November 20, 2007 at 20:50:16 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
yes I tired to RDP without the port number on the end 69.134.148.31 is my RR ip address and 192.168.1.1 is my router port.

Report Offensive Follow Up For Removal

Response Number 13
Name: Curt R
Date: November 20, 2007 at 22:12:02 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Ok, try connecting with RDP without the port number at the end. What happens then?

Report Offensive Follow Up For Removal

Response Number 14
Name: Jrb599
Date: November 21, 2007 at 07:23:00 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
Same thing, I can't get in.

Report Offensive Follow Up For Removal

Response Number 15
Name: wanderer
Date: November 21, 2007 at 10:42:14 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
DID you add that port number to your router and FORWARD it to your server?


Imagine the power if you knew how to internet search


Report Offensive Follow Up For Removal

Response Number 16
Name: Intel 80486 (by meisinscotland)
Date: November 22, 2007 at 20:41:20 Pacific
Subject: Windows 2000 Server problems
Reply: (edit)
2K server doesn't have a firewall but it has IPSec, which is as good as if you know how to use it.

I didn't know it existed until recently.

    
 

My blog


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Windows 2000 Server problems

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




XP Installed to G?

exessive internet traffic

ZoneAlarm Question. Blocked Connect

Windows Live Messenger Problem

Delete $Uninstall after SP3 updates


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC