Windows server 2003 Remote desktop over WAN problem.

Ok so problem is there is a 2003 windows server in my office. Any computer phone etc. can connect to it via Remote desktop if they are in the LAN network. I have port forwarded 3389 , disabled firewalls , there is no antivirus software on the server.
BUT I cannon log in over WAN. Heres the problem.
I type in the WAN ip I connect with credentials.
This is what i get:
Connecting...
Negotiating credentials...
Then it just suddenly force closes.
Also tried from a Windows 8 PC , when trying to connect it INSTANTLY throws me an error saying:
This computer cant connect to the remote computer. If the problem continues contact etc..
No matter where i try , a pc , a laptop , a phone , a tablet it just force closes. I can see that the devices are able to see the server and are trying to connect , but the connection just force closes for no reason and no error is shown. Also I dont see
anything in the event viewer on the server. The credentials are correct also. And the port is forwarded correctly.
Where could the problem be?

Hi,
Thank you for posting in Windows Server Forum.
As you have commented that you have forwarded port correctly at windows end, but still suggest you to check whether you have port forwarded on Router which you are using for WAN connections.
Can your local system can make successful ping to the remote server from WAN connections?
For testing you can telnet <router ip> 3389 and if you get blank screen then it confirm that port has been forwarded.
It might happens that there is port assignment conflict taken place, so check with “netstat –a –o” and see port 3389 is not being used by other application, if that is the case then change the port.
You can refer following article for more troubleshooting steps (Point 2)
Remote Desktop disconnected or can’t connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2003
http://support.microsoft.com/kb/2477023
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Similar Messages

After MS13-098 and SecurityAdvisory(2915720), Windows Server 2003 Remote Desktop(TermService) cannot start service

I have trouble with Windows Server 2003 R2 Standard. I installed the KB2893294(MS13-098) patch, and I changed the registry that is suggested actions of Security Advisory(2915720) http://technet.microsoft.com/en-us/security/advisory/2915720
Suggested Actions:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config]
"EnableCertPaddingCheck"="1"
After rebooting the event viewer(system) says:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
User: N/A
Description:
Cannot load illegal module: C:\Windows\system32\rdpwsx.DLL
After I cannot use Remote Desktop Connection from other client.
So I check the all security patches and other hotfixies. I checked the KB2653956 and KB958476.
But TermService do not recover the error.
And then, I delete the "EnableCertPaddingCheck" registry and reboot systems.
TermService have no error. I can use Remote Desktop Connection from other client.
After KB2893294 installed, Remote Desktop Connection cannot use from other client that "EnableCertPaddingCheck" registry set to "1".
Other Windows Server 2008 systems do not effect the KB2893294 patch. But All Windows Server 2003 systems cannot use the Remote Desktop Connections after the KB2893294 patch.

Update on this issue:
The debug team has accepted the issue and has identified it as a regression. Right now they're targeting *June* as the release date for a fix. I'm attempting to educate them that customers don't just install patches the day (or even month) they're
released and that the fix needs to be moved up in priority to give a minimum of 60 days to install the patch before the time-bomb explodes.
In the meantime, a workaround has been provided that will turn off the new functionality. Note that I have not yet had a chance to test this. It entails creating a new DWORD registry entry--UseLegacyPE--and setting it to 1.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ImageHlp\UseLegacyPE
I will update this thread when I have further information.

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

Probably. You may be able to use Finder > Go > Connect to server to access the server. You may be able to share folders using Remote Desktop too. Whichever one you like the best.

Windows Server 2003 DC / ADC Domain Join Problem

Hi,
I have Windows Server 2003 DC configured. It is Catalog Server and it holds all the fsmo roles .Also DNS Server too.
Now I created an additional domain Controller (ADC) _ dns server + i made it a global catalog server too,
The problem is when i shutdown my dc, I am not able to join client machines to the domain.
It says " The domain controller could not be contacted"
DNS Successful queried srv records..
the following domain controllers were found:
In the client pc , i have set up dns of dc and alternate dns of adc.
Why is this problem occurring?
Samvit

It says " The domain controller could not be contacted"
This is a DNS resolution problem.
Please make sure that each of your DCs is:
Pointing to the other one as primary DNS server
Points to its private IP address as secondary one
Points to 127.0.0.1 as third DNS server
Once done, restart netlogon service and run ipconfig /registerdns. For client computers, you need to make sure that they point to both DCs as primary and secondary DNS servers. As for the public DNS servers, they need to be configured on
your DCs as forwarders.
More details about recommendations for DCs IP settings here: http://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx
If this does not help the please check that there is no filtering between DCs and clients with DCs.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Can't change search options in Outlook 2007 on Windows Server 2008R2 Remote Desktop Users

One of my users is trying to change search options in Outlook 2007.
But he can't change the search options.
He is working with Outlook 2007 on Remote Desktop Services 2008 r2.
We doen't use cache mode on terminal server.
Any sugesstion how we can enabling search options for remote desktop users ?

Hi Roel,
Thank you for posting in Windows Server Forum.
To customize Instant Search options by using Group Policy
- In Group Policy, load the Office Outlook 2007 template (Outlk12.adm).
- To customize how results are displayed, under
User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options\Preferences\Search Options, double-click the setting that you want to set. For example, double-click Turn off wordwheel.
- Click Enabled. For hit highlighting color, choose a color from the Background Color drop-down list.
- Click OK.
More information.
Configure Instant Search options in Outlook 2007
http://technet.microsoft.com/en-in/library/cc178983(v=office.12).aspx
In addition, perform below steps to edit the registry key and check.
Step 1: Open the Registry Editor application.
Step 2: In the Registry Editor, click the Edit menu and select Find. Type PreventIndexingOutlook in the search field and click Find Next.
Step 3: Right click PreventIndexingOutlook and select Modify. Change its Value data to
0 and click OK.
Step 4: Search again by clicking the Edit menu and select Find. Type SetupCompletedSuccessfully in the search field and click Find Next. Locate this key.
Step 5: Right click the SetupCompletedSuccessfully key and select Modify. Change its Value Data to 0 and click OK.
Step 6: Restart your computer and you will now be able to perform advanced searches in Microsoft Outlook.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Remotely login error on windows server 2003 using gemalto smart card

I am getting this error when trying to log on windows server 2003 remotely using smartcard. We have our own CA. We are able to successfully logon on windows server 2008 using same card.

Hi,
Base on my research, Event 537 indicates that a logon attempt was made and rejected for some reason other than those covered by explicit audit records in this category.
Would you please provide more details?
Are there any related warnings and errors under Application Logs or System Logs?
By remotely login, do you mean logon via RDP?
Here are some related links below for you references:
Event 537
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.0&EvtID=537&EvtSrc=Security&LCID=1033
Smart Card and Remote Desktop Services
http://technet.microsoft.com/en-us/library/ff404286(v=WS.10).aspx
Please get back to us with the necessary information at your earliest convenience.
Best Regards,
Amy Wang

Error running universall installer using Oracle 11g on Windows server 2003

Hi,
I want to uninstall Oracle 11g on Windows server 2003 and when I run universall installer I receive the following error
Checking swap space: 0 MB available, 500 MB required.
Please advise how to resolve this error and the procedure to uninstall Oracle 11g on Windows server 2003
Thanks,
Ant

Hi;
For swap problem, please check:
Swap space problem on Windows XP
http://www.pcnineoneone.com/howto/swpfile1.html
For remove process please check:
Oracle 11g on Windows Srv 2003
WIN: Manually Removing all Oracle Components on Microsoft Windows Platforms [ID 124353.1]
Regard
Helios

How to enable users to access windows 2012 through remote desktop client on windows XP SP3

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.
Have you tried adding those users to the "Remote Desktop Users" group? It's in Active Directory Users and Computers and it's a Built-In group. Might want to give that a try ...
- JJ

Crystal Reports version 10.0.0.53327 supported on Windows Server 2003 R2?

Hello,
We are currently using Crystal Reports version 10.0.0.53327 with a ASP web application on Windows 2000 Server. We are in the process of upgrading the web server to Windows Server 2003 R2 but have encountered problems with the print feature in the application when printing reports using Crystal Reports. We have duplicated every setting from the original web server on the new web server down to each registry entry and DLL file for Crystal Reports but continue to have a problem. Are there any known compatibility issues with our version of CR and Windows Server 2003 R2?
Any information or assistance provided will be greatly appreciated.
Morgan

You are not giving enough info re. the actual issue. E.g.; encountered problems with the print feature is a bit "loosy goosy". What are the details of the printing issue? Errors? Incorrect printing? Etc.
Taking a wild guess here, but do have a look at [this|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do] kbase.
If that does not help, do search these forums as well as the kbase:
https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_ossnotes&query=&adv=true
And if that does not help, provide more info. Oh, also search for latest updates for CR 10 here:
http://service.sap.com/sap/bc/bsp/spn/bobj_download/main.htm
And finally, specify how you deploy the CR 10 runtime to that server.
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup

I am trying to remote into a Windows Server 2003 from a Windows 7 machine and having issues

I am trying to remote into a Windows Server 2003 from a Windows 7 machine. It says "The terminal server has exceeded the maximum number of allowed connections".
My first stop in trying to solve this problem was here:
[URL="http://www.howtogeek.com/howto/windows/command-line-hack-for-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"]howtogeek.com[/URL]
And it says:
[I]
[INDENT]This problem happens because Windows only allows two remote terminal services connections when you are in administrative mode, and you’ve either got two people already on that server, or more likely, you’ve got a disconnected session that still thinks
it is active.
The problem with this error is that you have to actually get on the server console to fix the problem if the server isn’t in a domain. ([B]If you are in a domain, then just open Terminal Services Manager and log off or disconnect the sessions[/B])[/INDENT][/I]
So it seems to suggest that all I have to do really is to run the Terminal Services Manager but I cannot find it.
This web site from mssqltips.com [URL="http://www.mssqltips.com/sqlservertip/1981/remote-desktop-error-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"](click here)[/URL] says all I need to do is first execute "mstsc /
admin" from the command line. But, when I do that, I get a message when I try to remote to the server, that says this: "To log on to this remote console session, you must have administrative permissions on this computer".
So, what now? What do you suggest?

Hi Bobby,
Yes, it is by design. By default, Windows Server only accepts two concurrent administrative sessions (Administrative Mode). It means that only two administrators can work on the server at
the same time.
If you would like more concurrent sessions, you need to purchase RDS CALs, install Terminal Services related server roles with proper configurations on the server.
Remote Desktop for Administration (server 2003)
http://technet.microsoft.com/en-us/library/cc785186(v=ws.10).aspx
What Is Terminal Services?
http://technet.microsoft.com/en-us/library/cc782486(v=ws.10).aspx
Terminal Services Configuration
http://technet.microsoft.com/en-us/library/cc787078(v=ws.10).aspx
Purchase client access licenses
http://technet.microsoft.com/en-us/library/3660ac5a-7468-48d3-b7e8-5529de8fb6c5
Thanks.
Jeremy Wu
TechNet Community Support

Windows Server 2003 and problem with SSL connection (TLS)

Hi,
We are forcing a problem with SLL/TLS connection on a machine Windows Server 2003 SP2.
We spent hours trying to solve it without any result.
SYMPTOMS
No SSL connection can be established in any application since last year, e.g.:
we cannot do any windows update, because there is a time verification over SSL on the windows update website (there is an error that the time is incorrect while it is up-to-date)
we cannot open any website in Internet Explorer over https
when we try to connect to the SQL Server (database SQL 2008 hosted on the same server) with Management Studio it fails with an error: "A connection
was successfully established with the server, but then an error occurred during the pre-login handshake.(provider: SSL Provider, error: 0 - Could not
contact LSA)(Microsoft SQL Server)"
in a custom applications which sends requests over https we receive an error: "Could not establish trust relationship for SSL/TLS secure channel"
Everything seems to point at some SSL problem somewhere deep inside Windows.
We installed several patches, but without any result.
Can anybody help?
Regards,
Dawid

Hi, thanks for answers,
- In IE both SSL2.0 and TLS1.0 are checked. We tried to disable TLS1.0 - with no results.
- In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\Schannel both SSL2.0
and TLS1.0 are enabled. We also tried to dislable TLS1.0 on the Client side - with no resuts.
- In
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL EventLogging is set to 3, so it should log warnings
and errors. But we cannot find any related logs in EventLog
Unfortunately we are still in the same place.

Windows Server 2003 (sp2 - 32bit) - OEM problem

I inherited this in-house (closed) system a few years ago and have not had a problem until a couple of months ago. It has been running for about 1 1/2 years.
Desc:   Oracle 11.1.0.6 (64bit) on Windows Server 2003 (sp2 - 32 bit)   [[ yes, I know, what the heck is a 64 bit Oracle running on a 32 bit windows?]]
     2 - instances running - one production with associated ASM, one RMAN cat with no ASM - all folders are backed up to a large SANS.
          - each instance has its own listener
          - each instance has its own dbconsole service
Problem:
1. a couple of months ago, when I attempted to access the production OEM, I started seeing
service-specific error 1 (0x1), NET HELPMSG 3547
     -- the first time this happened, I immediately opened the OEM for rman and it was successful
          It was also fortunate in that we were doing some power upgrades and all of our systems were shutdown - and after this system was powered on, the production OEM worked fine.
     -- a few weeks later, the prod OEM was not accessible - giving the same 3547 error. We were not able to shut down, so I stopped the Windows services for this instance, and stopped
               the windows listener services for both instances. I then started only the production windows services, and was able to use the prod OEM. Then I started the listener service for
               the rman and all was well.
     -- this Monday (today is Thurs), the prod OEM was inaccessible again and I tried the stopping and restarting of the services and started seeing 7024 errors. I tested the rman OEM and
          it was fine. I stopped both instances via sqlplus commands, used emctl to stop both dbconsoles (of course, the prod one was already not running), shut down the ASM instance and
          then stopped all the Windows services. then I only brought up the prod services and confirmed with sqlplus commands that everything was started - but the final service, dbconsole
          would not start. This morning I was able to reboot the server (after shutting down all the Oracle services) and now I can access the prod and the rman OEMs.
2. What the heck?   Because I can get the prod OEM working with just a reboot, I don't know if I should have to rebuild dbconsole.   And since I'm the only one disuncombullated because
          of the prod OEM, it is not a fall-down-crying situation - I'm actually a sqlplus kinda guy, but when I'm just doing visual maintenance, it is nice to view OEM remotely for a quick check.
3. I've been working with Linux systems and Oracle for many years and I've never experienced this kind of problem.   Oh, and since it is a closed system, it will be when pigs sprout wings
               and start flyng that I'll be allowed to install patches - but again, if a reboot 'fixes' this issue, what the heck? Oh, finally, I don't believe in the common windows fix of rebooting - I'd
               like to find out WHY this is happening and literally fix it.
ANYBODY have a clue?   Not me...
Thanks for your time.

user12183171 wrote:
I inherited this in-house (closed) system a few years ago and have not had a problem until a couple of months ago. It has been running for about 1 1/2 years.
Desc:   Oracle 11.1.0.6 (64bit) on Windows Server 2003 (sp2 - 32 bit)   [[ yes, I know, what the heck is a 64 bit Oracle running on a 32 bit windows?]]
You'd better double check that. It is fundamentally impossible for 64-bit software to run on a 32-bit OS.
     2 - instances running - one production with associated ASM, one RMAN cat with no ASM - all folders are backed up to a large SANS.
          - each instance has its own listener
One single listener, with the default name of LISTENER, using the default port of 1521, is quite capable of -- indeed, was designed to -- service multiple instances of multiple versions running from multiple homes.
          - each instance has its own dbconsole service
Problem:
1. a couple of months ago, when I attempted to access the production OEM, I started seeing
service-specific error 1 (0x1), NET HELPMSG 3547
     -- the first time this happened, I immediately opened the OEM for rman and it was successful
          It was also fortunate in that we were doing some power upgrades and all of our systems were shutdown - and after this system was powered on, the production OEM worked fine.
     -- a few weeks later, the prod OEM was not accessible - giving the same 3547 error. We were not able to shut down, so I stopped the Windows services for this instance, and stopped
               the windows listener services for both instances. I then started only the production windows services, and was able to use the prod OEM. Then I started the listener service for
               the rman and all was well.
     -- this Monday (today is Thurs), the prod OEM was inaccessible again and I tried the stopping and restarting of the services and started seeing 7024 errors. I tested the rman OEM and
          it was fine. I stopped both instances via sqlplus commands, used emctl to stop both dbconsoles (of course, the prod one was already not running), shut down the ASM instance and
          then stopped all the Windows services. then I only brought up the prod services and confirmed with sqlplus commands that everything was started - but the final service, dbconsole
          would not start. This morning I was able to reboot the server (after shutting down all the Oracle services) and now I can access the prod and the rman OEMs.
2. What the heck?   Because I can get the prod OEM working with just a reboot, I don't know if I should have to rebuild dbconsole.   And since I'm the only one disuncombullated because
          of the prod OEM, it is not a fall-down-crying situation - I'm actually a sqlplus kinda guy, but when I'm just doing visual maintenance, it is nice to view OEM remotely for a quick check.
3. I've been working with Linux systems and Oracle for many years and I've never experienced this kind of problem.   Oh, and since it is a closed system, it will be when pigs sprout wings
               and start flyng that I'll be allowed to install patches - but again, if a reboot 'fixes' this issue, what the heck? Oh, finally, I don't believe in the common windows fix of rebooting - I'd
               like to find out WHY this is happening and literally fix it.
ANYBODY have a clue?   Not me...
Thanks for your time.

JNLP prompted to Save (only) in Windows Server 2003 SP1 over https

In Windows Server 2003 when using https to download the jnlp and jars, IE 6.0 prompts to Save the jnlp file. It does not give the option to open it straight from IE..
The IE settings are:
Do not save encrypted files to disk - off/unchecked
Empty Temp Internet Files when browser is closed - off/unchecked
Using Apache and Tomcat5 with the Mime type set correctly to application/x-java-jnlp-file.
When using http, the jnlp launches web start just fine.
When using https on WinXP and Win2000, the jnlp launches just fine.
It seems to be a Win2003Svr/IE security check that will not allow the jnlp to be launched directly.
There have been a few mentions of this on the web, but no solutions have been posted that I could find.
I am using jre 1.4.2_06. I tried 1.4.2_08 because that WebStart security bug was fixed, but the same issue was occurring. It seems like IE is doing it.
It doesn't get to WebStart until after saving the file and then double clicking it.
I have tried most of the IE settings to see if they helped, but to no avail...

Hello.
I'm glad someone brought this problem up.
We have about 1000 external customers using webstart for approx. 3 years with runtimes
varying from 1.4.1_XX to 1.5.0_XX. We have the same problem with some customers being prompted by a dialog and what to do with the JNLP file. When these customers try a testing link to a webstart app over HTTP they are not prompted. Only when using our business app. over HTTPS and with Internet Explorer. This behavior does not occur only in Win server 2003 but in several
OS from Windows 2000 , XP Home/Pro SP1 SP2 , Citrix Metframe ..you name it. We have known this for years now and not being able to do something about it since we can't reproduce it. All I know for sure is that IE is behind it all and it's not surprising since it is a part of the OS. When using other browsers like Mozilla or FireFox, it works fine.
The customers are now forced to save the JNLP file and launch the app that way. Not acceptable
Is there some registry change that someone knows of to correct this problem.
Regards
Johan

SMB Extremely Slow over VPN With Windows Server 2003

Hello everyone,
I finally convinced another person at my law firm to switch to a MacBook Pro. In preparation, I am attempting to fix any compatibility problems that would put off this new user. Unfortunately, our IT guy recently switched us to a Sonicwall SSL-VPN 200. I can connect to our server through the VPN client with no problems and I can mount our internal file server, but the connection is incredibly slow. My initial reaction was that it must be a problem with Windows Server 2003 and SMB, but I was previously able to connect to and operate on our VPN through our old Fortinet (ipsec) device with no problems. Simply put, directory switching, file moving, etc. are all now incredibly slow over the VPN. Help!

Full support for SMB signing did not appear until Samba 3.0.2 released in 2004. Mac OS X 10.5 (Leopard) supports SMB signing. Previous versions require either disabling SMB signing server-side, using a third party SMB client, using the command-line smbclient program, or updating samba yourself.

Add-on installation problem in Windows Server 2003

Hi guys,
I have a problem when i want to install my add-on in the Windows Server 2003. The server gives me error :
Unable to load AddOnInstallAPI.dll
and when i try install using the same installer at the client station, everything is ok.
Does anybody have suggestion about that problem? I suspect the problem is the Windows' security that did not allowed me to load the .dll. Does anybody know how to set the security?
Thanks you,
Harianto Ng

I've found an answer on the similar question here, on the forum, saying that Windows 2003 is not a supported SAPBO Client OS.
In my experience I could not even set a reference to SAPbouicom.exe with a message "cannot load DLL"...
Natalya

Windows server 2003 Remote desktop over WAN problem.

Similar Messages

Maybe you are looking for