I cannot rdp to sbs 2003 server after repair install inside or outside firewall : Microsoft, Small Business Server, 2003, This server is the Domain Controller.

May 17, 2008 01:29am pdt

1. TechSoEasy 589,227
2. RobWill 348,566
3. KCTS 142,774
4. Sembee 125,597
5. kieran_b 91,862
6. Dave_AND 90,993
7. mwecompu... 85,930
8. leew 79,627
9. olafdc 74,402
10. suppsaws 69,651
11. DrDave242 68,633
12. MrManderson 68,455
13. SysExpert 45,630
14. 18526 44,870
15. ormerodr... 44,293

1. TechSoEasy 5,981,216
2. Sembee 780,429
3. RobWill 557,256
4. olafdc 538,367
5. leew 452,493
6. KCTS 388,529
7. suppsaws 257,016
8. redseate... 248,724
9. vico1 205,195
10. Dave_AND 175,108
11. MrManderson 166,963
12. keith_al... 163,836
13. MPECSInc 144,854
14. tigermatt 141,769
15. sguinn100 135,295

05.07.2008 at 12:34PM PDT, ID: 23384029

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.0

I cannot rdp to sbs 2003 server after repair install inside or outside firewall

Zones: SBS Small Business Server, Windows 2003 Server, Remote Desktop/Terminal Services

Tags: Microsoft, Small Business Server, 2003, This server is the Domain Controller.

The RAID card went bad in this SBS 2003 domain controller, and we could not get an exact match of the card ASAP so went with another card, which precipitated a repair install on the server, followed by redoing the updates and patches to current. After this, all seems to be working well except that we cannot rdp to the server by name or IP address inside or outside the firewall. They never used to rdp to it before from outside, but it worked fine from the inside using the standard 2 available connections. Nothing has changed in the firewall device, and the IP is the same on the server. The services are all running, and it has been rebooted three times and all related services that I know of stopped and started. Please help!

Start your free trial to view this solution

Question Stats

Zone: OS

Question Asked By: badmojo1977

Solution Provided By: RobWill

Participating Experts: 3

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

05.07.2008 at 12:46PM PDT, ID: 21519723

cmcoadmin:

Hate to state the obvious, but after the repair install, you verified that remote desktop is enabled (Start -> Control Panel -> System -> Remote -> Enable Remote Desktop) and that the proper users are setup?

05.07.2008 at 12:55PM PDT, ID: 21519812

badmojo1977:

Yes, we did have to reenable it and add users, but it still wouldn't allow connections. It pops up with the "This computer can't connect to the remote computer. Try connecting again. If the problem continues contact your network administrator" box within 2 seconds. Almost instantly. This happens from multiple workstations.

05.07.2008 at 01:03PM PDT, ID: 21519880

cmcoadmin:

Can the client computers contact that server at all, via ping or thru a file share?

05.07.2008 at 01:05PM PDT, ID: 21519899

naldiian:

Try to telnet to the server on port 3389 to see if you get a response, indicating that there is a service on the server that is listening on that port. That will tell you if Terminal Services is actually listening for connections to help identify where the problem might be.

If you get no response and the command prompt eventually responds that the connection attempt times out, you have a server that is not running Terminal Services (at least not in a functional condition, or your Terminal Services is configured to listen on a different port than the standard one. At that point, I would just remove Terminal Services from the server, and then reboot and add it back.

05.07.2008 at 01:06PM PDT, ID: 21519905

badmojo1977:

It can be pinged by name or ip address, and shares can be accessed.

05.07.2008 at 01:06PM PDT, ID: 21519910

naldiian:

Sorry, meant ADD terminal services via Windows Components and then remove it after a reboot.

05.07.2008 at 01:13PM PDT, ID: 21519971

badmojo1977:

Well, telnet does indeed fail, however, apparently because it's an SBS server, the only Terminal Services choise I get in Add/Remove programs is Terminal Server Licensing, and when I added, rebooted, removed, rebooted that, nothing changed.

05.07.2008 at 01:43PM PDT, ID: 21520205

Rank: Sage

RobWill:

After some Windows updates, it is necessary to reboot the server a second time before being able to connect using an RDP session. Have you done so?

If one of the updates was SP 2 see the following site regarding known issues with Remote Desktop after installation of SP (4th group of links).
http://www.lan-2-wan.com/2003-SP2.htm

See if the service is running on the server by making sure it is "listening" for your connection. To do so at a command line enter (substitute port # if not using default 3389):
netstat -an |find "3389"
You should get the following result:
TCP 0.0.0.0:3389 0.0.0.0:0 listening
If not go to Start | Run | services.msc and see if Terminal Services is started and set to automatic

05.07.2008 at 01:49PM PDT, ID: 21520245

badmojo1977:

Yup, we have rebooted the server 5 times since then. As far as the SP2 post installation problems, I found that thru researching and installed the fix for it, but it didn't help unfortunately. The service is running and listening correctly.

05.07.2008 at 04:04PM PDT, ID: 21521116

naldiian:

Your last post mentions that the service is running and listening correctly, yet you previously stated that the Telnet attempt failed to reach a service listening on 3389. It cannot be both...

Are you certain that the Windows Firewall is not running? I wonder if after a restore it reverts to default configuration, which would block RDP connections without being updated. The reason you normally dont have to manually add exceptions for RDP on the firewall configuration is that when you enable remote administration connectivity when first setting it up it adds the exception rule for you at that time. After a restore, if the firewall lost its configuration data it might block RDP and yet not automatically add the exception due to the Terminal Services component being configured already and not thinkint it needs to check that ever again.

Just a guess there, and I would think other things might be problematic as well if that were the cause, but who knows...

05.07.2008 at 04:09PM PDT, ID: 21521143

Rank: Sage

RobWill:

Try running a remote desktop session from the actual console (yes this works). If it works then that confirms it is a firewall or port forward issue.

05.07.2008 at 05:23PM PDT, ID: 21521450

badmojo1977:

naldiian: Yea that seemed strange to me too. When I run a telnet test on port 3389 to that server ip, it just blinks till it times out back to the command prompt. However, when I run a netstat test it returns the result TCP 0.0.0.0:3389 0.0.0.0:0 listening just as it should.

to naldiian and RobWill: I will attempt to run a console based rdp session and double check the firewall settings as soon as the backup job is completed this evening. WIll get back to you ASAP!

05.07.2008 at 05:36PM PDT, ID: 21521509

Rank: Sage

RobWill:

What do you mean by "just blinks till it times out back to the command prompt"? If you telnet to the server on port 3389 (telnet 123.123.123.123 3389) and the connection is successful, you will get a blank screen with a flashing underscore cursor (i.e. no prompt or response). If it fails you will get an error or time out.
Based on that, might it have been a successful connection?

05.07.2008 at 06:13PM PDT, ID: 21521649

badmojo1977:

Yup, that means it was successful. I've got lots to learn about Telnet apparently.

05.07.2008 at 06:32PM PDT, ID: 21521721

Rank: Sage

RobWill:

You and me both :-)

Let us know when you have a chance to try from the console.

05.07.2008 at 06:35PM PDT, ID: 21521732

Rank: Sage

RobWill:

You mentioned you cannot "RDP" to the server, so I assume you are referring to a Remote Desktop Session. her you have SBS, have you tried Remote Web Workplace, just out of curiosity. The both use the same protocol but there are some differences, such as external ports used.

Grasping at straws.

05.08.2008 at 12:27PM PDT, ID: 21527699

badmojo1977:

Sorry about the delay. Had a meltdown with a different server. So I tried to run a connection from the conosle of the server with the problems, and still no go. Would not connect even from there, so apparently it's not a port or firewall problem. Anyone have any other ideas? Maybe a way to uninstall and reinstall TS on an SBS server?

05.08.2008 at 12:33PM PDT, ID: 21527745

badmojo1977:

Oh, and also, it fails thru remote web workplace as well.

05.08.2008 at 02:58PM PDT, ID: 21528823

Rank: Sage

RobWill:

To be honest I have never heard of doing a repair install with SBS. Good to hear it went this well. Have you since re-applied Service packs? If not see the order in which to apply below.
I am pretty much stumped.

Best practices states SBS Service packs should be installed in the following order:
Windows Server 2003 SP1
Exchange Server 2003 SP1
Windows SharePoint Services SP1
Windows Small Business Server 2003 Update KB891193 for Windows XP Service Pack 2
Windows Small Business Server 2003 SP1
ISA 2004 SP1 (If SBS premium and ISA installed)
SQL 2000 SP4 (If SBS premium and SQL installed)
Exchange Server 2003 SP2
Windows Server 2003 SP2

Accepted Solution

05.12.2008 at 08:09AM PDT, ID: 21547620

badmojo1977:

Well I redid the repair install and then redid the service packs in this order, and it came back to life! Thank you very much gentlemen

05.12.2008 at 12:06PM PDT, ID: 21549645

Rank: Sage

RobWill:

Good to hear. Thanks badmojo1977.
Cheers !
--Rob

20080236-EE-VQP-29 / EE_QW_2_20070628