Sign in to follow this  
Followers 0
Alexander Dreyer

Windows Server 2008 R2 RDS Profiles cannot use ICMP

9 posts in this topic

Hi all

 

I'm having an issue on Windows Server 2008 R2 system configured with RDS(Terminal Server). Now the Issue is simple. If I try to ping from the Administrator profile i get reponses and all is good however when I try to ping from one of the normal user profiles I get a Ping Transmit Failure: General Failure Error. This is very strange as no firewall Rules blocks ICMP in any direction neither does group policy objects limit users from using the Ping command and everything is happening on the same computer. I need ICMP ping messaging to work from the user profiles for the biometrics systtem that verifies device connectivity using ICMP ping command.

Does anybody have suggestions?

Share this post


Link to post
Share on other sites

Are you running AV on this box that would be different for users than admin?

Are you pinging by name or IP, can they ping loopback 127.0.0.1

Share this post


Link to post
Share on other sites

Hi,

I'm only running Bitdefender for file servers but that actually runs on the administrator profile. If I promote a normal User account to Administrator he is able to ping. This is however not a solution. Pinging by name, IP Address and pinging localhost all give the same result: Ping Transmit Failure: General Failure.

Share this post


Link to post
Share on other sites

Hello,

Hi,

I'm only running Bitdefender for file servers but that actually runs on the administrator profile. If I promote a normal User account to Administrator he is able to ping. This is however not a solution. Pinging by name, IP Address and pinging localhost all give the same result: Ping Transmit Failure: General Failure.

Well, it seems since Bitdefender is running as admin (from what I understand) anything below it will automatically deny it.

You would have to set permissions for each user.

(Long shot in the dark since you said it runs as admin)

Share this post


Link to post
Share on other sites

What groups are these users members of that remote to this server?

Share this post


Link to post
Share on other sites

Bitdefender actually runs as a SYSTEM service. Disabling bitdefender has no effect on the issue. The Bitdefender module does not include a firewall or any network protection. It's purely for file level scan and protection. We use Windows Firewall. The issue is strange.

Share this post


Link to post
Share on other sites

What groups are these users members of that remote to this server?

The users are memebers of the "Users" Group and also a memeber of the Remote Desktop Users. We have a few terminal servers in production. None of them however had this issue. All of them have simillar security setups and run bitdefender. By default all profiles should be able to use the ICMP protocol, unless the Admin specifically limits ICMP using a firewall rule. Which I also looked at and all ICMP rules are set to allow for all network locations.

Share this post


Link to post
Share on other sites

yeah very odd.. Does this server have more than 1 nic?

Share this post


Link to post
Share on other sites

it's UAC acting up with an outdated NIC driver, I've seen it

The ping executable tries to bind with the interface, the driver ###### up the elevation and UAC blocks it.

 

Either disable UAC or find a working NIC driver

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.