Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Server 2008r2 Terminal Server only accepting local connections

Posted on 2013-05-22
2
Medium Priority
?
470 Views
Last Modified: 2013-05-22
The local LAN and Terminal Server recently underwent a internal IP address conversion but it was working for a couple days after the fact.  Then suddenly yesterday it started only accepting LAN addresses.  Anyone connecting from another site or externally to the company receives the error.  "Remote Desktop can't connect to the remote computer for one of these reasons:"

So, Immediately I think Firewall.  The firewall is disabled on the terminal server.  All profiles, domain, private and public profiles are off.  Then I think it must be the perimeter firewall, but if that were the case then the remote site should still work.  I did check the perimeter firewall as well and the security and nat policies are correct.

I did several telnet tests externally and I can see the traffic going through the firewall fine.  However, nothing shows up in the event logs on the terminal server for these connections.  So the traffic does not look to be making it to the server at all but I can't find what that would be.

There is a server based AV running (kasperski) but it doesn't have a firewall component installed.  I have tried disabling that as well without any change.

I can't figure this out!!
0
Comment
Question by:-Darvin-
  • 2
2 Comments
 

Author Comment

by:-Darvin-
ID: 39187401
I have since uninstalled kasperski and enabled / disabled the windows firewall service with no changes in behavior.
0
 

Accepted Solution

by:
-Darvin- earned 0 total points
ID: 39188086
I FINALLY found the solution to this problem!  I was checking connectivity on the server and it said it had internet access but I found I was unable to ping external addresses by name or IP.  I can hardly believe none of the internal users mentioned that internet access was down from that server but it was.

I checked the network connection and all seemed well.  The static address, DNS and gateway were all correct.  The network and sharing map showed we did have internet access but in fact did not.

IPConfig /all showed the problem.  In the default gateway area two addresses were listed 0.0.0.0 and our normal gateway below.

I did route delete 0.0.0.0 to remove it and it did but also removed our normal default gateway.  I re-assigned that back to the nic.  I was then able to ping external names and addresses as well as connect normally.

Hope this helps someone else because it made me miserable.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

At the beginning of the year, the IT world was taken hostage by the shareholders of LogMeIn. Their free product, which had been free for ten years, all of the sudden became a "pay" product. Now, I am the first person who will say that software maker…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

916 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question