Windows 8/7 can't connect to RDS GW.

Hey..
We have 2 RDSH, 1 GW, 1Licenseand 1 fileserver(roamingprofiles), all running on 2012 R2.
Also a Alpha SSL cert - Wildcard.
Everytime we try to connect we get a message in event Viewer saying:
"The user "domain\user", on client computer "ip", did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server. The authentication method used was: "NTLM" and
connection protocol used: "HTTP". The following error occurred: "23003".
Now we have check the CAP and NPS rules and even receatived then to.
And now we are stuck.

Hi,
Thanks for your comment. Sorry for late response.
You are facing Event ID 201 for RD Gateway and for that probable solution is to recheck the following points.
To determine whether a client meets the requirements of at least one RD CAP, do the following:
• Check the RD CAP settings on the RD Gateway server. For instructions, see "Check RD CAP settings on the RD Gateway server" later in this topic.
• Ensure that the local or Active Directory security group specified in the RD CAP exists, and that the user account (and if applicable, the computer account) for the client is a member of the appropriate security group. For instructions for Active Directory
security groups, see "Confirm that the Active Directory security group specified in the RD CAP exists, and check account membership for the client in this group." For instructions for local security groups, see "Confirm that the local security
group specified in the RD CAP exists, and check account membership for the client in this group" later in this topic.
More information.
Event ID 201 — RD Gateway Server Connections
http://technet.microsoft.com/en-us/library/ee891053(v=ws.10).aspx
In addition, create RD Gateway managed groups under RD RAP and enter the farm name with each server name under that group and after that try to connect, please go through
this article for detail. Apart for try you can uncheck the option “Bypass RD Gateway for local address”
and verify.
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]

Similar Messages

Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
or what's the problem,
Mahmoud Sabry IT System Engineer

this issue maybe will be fix by latest version, we still waiting for it
maybe your issue can be fix using this methods
https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
http://shawn.meunier.com/?p=1#comment-43

Pc with windows xl/sp3 can't connect / acquire ip address from airport extreme; meanwhile, my macbook in connecting fine. We have a wpa2 personal password

My husband's Dell with Windows xl (sp3) can't get an ip address from our new airport extreme. Nor can my daughter's Windows 7 computer. There are no firewalls in place. Both computers worked with my old Airport, though it was sssslllllllowwww. My Macbook works fine and is super fast compared to the old airport. We are using a wpa2 personal password.
Anyone out there have a cure for this problem so we can hook up those sad pcs?
Thanks a lot.
Elizabeth

First, make sure that the new Airport is configured exactly the same as the old one. Hopefully you saved the configuration settings in a file and can look at them to be sure.
If the Windows PC's can't connect with the same password, it's possible that the PC's were using an older wifi protocol like 802.11a or b. The new Airport is backwards compatible but has to be setup that way check to see what versions of 802.11a the windows computers support and make sure that the wireless mode of the airport is setup to accomodate them.
Can the PC's get an IP address if they are connected to the AirPort using an ethernet cable? If they can, that would help naorrow things down to a wireless issue and not some other configuration problem.

Windows 8 PC can't connect to Verizon Jetpack MiFi 5510L

I have a Verizon Jetpack MiFi 5510L and I am unable to get my Windows 8.1 PC to connect to the Jetpack. My iPhone 5 with iOS 7.0.4 and my Lenovo T400 running Windows 7 Ultimate can both connect to the Jetpack with no issue or changing of settings. The Jetpack's WiFi network is visible to my Windows 8 PC (ASUS V500c), but the Windows 8.1 PC cannot connect to it. The Windows 8.1 PC connects to my home wireless network and wireless hotspots in multiple locations just fine. Any help would be appreciated.

I tried everything in the posts, several times, without success, since I'm not sure what parameters to provide. For example, set profileparameter name=<name> authentication=wpa encryption=tkip authMode=userOnly returns an error message The oneX setting in the profile <profile> on interface "Wi-Fi" is not enabled. I've fiddled with a few settings, but nothing that seems to work.
A coherent, step by step, solution would be nice.

Windows 8, Error: "Can't connect to this network"

I have wracked my brain, my colleague’s brains, and used my googlefu to no avail.
I have a Win8 basic (cheapest OS) HP tablet 1000G2 that I am having troubles with. I have a network that requires WPA2-Enterprise with PEAP. It will not connect to this network, it will however connect to a neighboring network without
any security settings. I have fixed this issue once before and the same fix is not working.
The kicker... I have another exact same tablet that we got the same day... No issues connecting
Problem: It does not take the security settings that the server is prompting for. It prompts me for my credentials, but gives this error: "Can't connect to this network"
I did research last time and the collective reason was that the security settings weren't correct.
Solution that worked last time:
Connect to a network with open sec settings.
Open network and sharing center
Change adapter settings.
Right click wireless adapter click status
Wireless properties.
Security tab.
Change my network settings
Reconnect to my network
The tablet has been fine until today. These steps above do not resolve the issue anymore.
THERE IS NO VIRUS PROTECTION BESIDES WHAT WINDOWS OFFERS ON THIS DEVICE!
Troubleshooting steps I have tried: deleting all the wlan profiles with
http://windows.microsoft.com/en-us/windows-8/manage-wireless-network-profiles
and used http://answers.microsoft.com/en-us/windows/forum/windows_8-networking/windows-8-laptop-wont-connect-to-the-wireless/256c8bd2-e11f-4746-b3aa-3e6eb8305b56 page.
Change any properties one at a time that I thought might deal with this.
Removed all HP bloatware/3rd party connection managers.
Troubleshooting I tried last time:
Uninstalled and installed adapter drivers.
Tried the windows diagnose
Googlefu "Can't connect to this network" and you come up with a bunch of pages I have clicked on them and none of the solutions have worked.
Please if you have any solutions let me know! I am at my wits end with this dang thing.

These are all logical ideas, but alas I have already checked all of this. We do not have any blocking other than credentials(which are not locked and are correct). The amount of connections would be determined by how many IP Addresses that I have(which is
a ton). Not the wireless router, because we have many other devices that connect to it just fine. No mac filter. No the other pc isn't connected. No it is only connecting to one network.
I should mention that this is in an enterprise and not an at home network. It is a WAP not Wireless Router.

Windows 7 client can't connect to Server 2008 R2 Print Server VM (ESXi 5.5)

I have an issue today that is driving me bonkers.
I recently came on-board to a company in my area as the system administrator and this network has everything and the kitchen sink wrong with the network layout, probably the worst I've seen and I'm slowly but surely fixing it day by day.....
Well today I decided I was going to spin up another VM from a template and make a Print Server, seems harmless right? --- I thought so too, added all of the printers to the server and did test pages, all was dandy, but then I tried to add the printers to
clients and other server and the real fun has begun, I'm truly perplexed now...
I added a VM to my esxi 5.5 cluster at work that is a 2008 R2 server with only print management on it. I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via
DNS. I can test printers directly from the print server successfully printing out test pages however whenever I try to map printers you know from the directory in 'devices and printers' from any of the Windows 7 clients or any of the other 2003/2008 servers
I get the classical "Windows cannot connect please check the network connection and make sure sure the printer is turned on". I disabled the windows firewall and I made the point to print GPO set to disabled and still no luck. Again I can print to
all of the printers internally inside of the VM (so I know it communicating to all of the printers), I just can't connect to the printers listed in the directory on any of external desktop/client, it's like so annoying. spent about 6 hours until my brain just
couldn't think anymore, was about to go BS on the VM.
The only thing I can think of, as I was driving home, is that there is a GPO on one of the DC that has a desginated print server policy set. But prior to last week the forest leve was 2000 and now it's 2003. I just don't know Server 2000 enough to know if GPO's
worked in the same way they do in 2003.
Right now printers are connected to other servers in a ad hoc mentality it seems, there has never been a true print server.
Anyone ever have this problem before?
I'm truly puzzled...

Hi Mid.Hudson-IT,
Before we begin ,we should ensure we have configured the printer server correctly .
Here is a link for reference of configuring the printer server .
Print server role: Configuring a print server
https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
"I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
If we can ping the print server from the client,we can ensure the connection to the printer server is good .
Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
If we cannot ping the print server ,we should troubleshoot the network issue firstly.
We also can check the event viewer for more information to troubleshoot this issue .
Best regards

Windows 7 laptop can't connect to new Airport Extreme.

I had a NetGear router, but got fed up of not being able to use all of my devices, so I bought the AirPort Extreme and use the NetGear as a modem (wireless turned off). Our iPads, iPhones, Macbook, Windows Vista laptop and desktop all connect fine, but I can't get the Windows 7 laptop to connect, even by ethernet.
It has connected but drops the connection intermittently and then sometimes it fails to get a connection at all. It can see the AirPort, but says it can't connect. This happens paticulalry if the laptp has been left to hibernate.
I have installed the AirPort utility and I have turned off the power option that turns off the wireless card. I have done all of the Windows updates, and I have updated the drivers from the manufacturer website.
Any ideas? (Don't say use the Mac, this is my sister's computer, not mine!!)
Thanks.

Thanks for clarifying. If you don't mind, let's double-check your extended-network setup configuration:
o Open AirPort Utility and select the Time Capsule (TC), and then, choose Manual Setup from the Base Station menu.
o Click AirPort in the toolbar, and then, click Wireless.
o Verify that both “Create a wireless network” from the Wireless Mode pop-up menu and “Allow this network to be extended” checkbox are selected.
o Next, select the 802.11n AirPort Extreme Base Station (AEBSn), and then, choose Manual Setup from the Base Station menu.
o Verify that “Extend a wireless network” has been selected from the Wireless Mode pop-up menu. Also verify that the correct Network Name is shown for the network you want the AEBSn to extend.
Do your settings match these?

T41 re-installed Windows XP, now can't connect to Internet

I recently re-installed windows XP, but now I can not connect to the internet. I downloaded an Ethernet Intel Pro driver, however when following the steps to complete installation, I do not have any options under "Network Controllers" it says this driver is not found.
Can someone please advise what drivers need to be installed in order to connect to the internet again via ethernet and wireless?

recently had update
Care to share which update?
Have tried many things
Care to share?
Please detail ALL you have done so far in the way of troubleshooting? Need this info to avoid the been there done that scenarios.

Windows XP client can't connect to AirPort Extreme AP with WEP enabled.

Hello,
I have big problem with Mac Mini AirPort Extreme working in AP mode with Windows XP client.
Some time ago, AP refuse to connect Windows XP clients (notebook) when WEP is enabled (40/128 bit, same problem), while before that, everything work perfect.
On other hand, iPhone can connect using WEP without an problem.
When WEP is turned off, XP client can connect but this is not acceptable for me.
I must notice that friend of mine have absolute SAME PROBLEM which rise almost at same time few months ago. They have Mac Mini and XP notebook (different then mine) which can not connect with WEP turned on, while his iPod touch work!
I guess that this happened due AirPort Firmware upgrade included in some of Apple software update.
Does anybody have similar problem or know the solution?
My AirPort Card Information:
Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 1.4.16.2
Current Wireless Network: Mac mini
Wireless Channel: 11
Tnx in advance.

mikikg, Welcome to the discussion area!
Sorry but this is a known issue.
The only solution is to get a real wireless router instead of using your Mac mini as a base station.

Can't connect to RDS

Hi,
I have some issues trying to connect to RDS server.
My RDS is configured on the port 80. In Homesite+ everything is ok, and I can connect without any problem.
In Coldfusion builder I got the message:
Unable to contact the RDS Server.
For input string: "*
I'm behind a proxy, do you know if I have to set other connection parameters?
Thank you,
Milo

Can you log a bug with all the details please?
-Bhakti!

Windows 8.1 can't connect internet

I install a windows 8.1 on my macbook pro, but it can't connect internet.Why? How to deal it?

How did you install windows? Boot camp assistant would have downloaded and installed drivers for you.
Download and install these
http://support.apple.com/kb/DL1720

Cisco Jabber Client for Windows 9.7 Can't Connect to Other IPSec VPN Clients Over Clustered ASAs

Environment:
2 x ASA 5540s (at two different data centers) configured as a VPN Load Balancing Cluster
Both ASAs are at version 8.4(5)6
IPSec VPN Client version: 5.0.07.440 (64-bit)
Jabber for Windows v9.7.0 build 18474
Issue:
If I am an IPSec VPN user…
I can use Jabber to another IPSec VPN user that is connected to the same ASA appliance.
I can’t use Jabber to another IPSec VPN user that is connected to the different ASA appliance that I am connected to.
In the hub-and-spoke design, where the VPN ASA is a hub, and the VPN client is a spoke; if you have two hubs clustered together, how does one spoke communicate with another spoke on the other hub in the cluster? (How to allow hairpinning to the other ASA)

Portu,
Thanks for your quick reply.
Unfortunately, I do not have access to the ASA logs nor would I be permitted to turn on the debug settings asked for above. I might be able to get the logs but it will take awhile and I suspect they wouldn't be helpful as this ASA supports thousands of clients, therefore, separating out my connection attempts from other clients would be difficult.
I can, though, do whatever you want on the Linux router. Looking over the firewall logs at the time of this problem, I don't see anything that looks suspicious such as dropped packets destined for the Windows client.
As I said in my original post, I'm not a networking expert - by any means - but I am willing to try anything to resolve this. (But I might need a bit of handholding if I need to set up a wireshark andor tcpdump.)
Thanks again.

Cisco Jabber Client for Windows 9.7 Can't Connect IPSec VPN Clients over two ASAs

Environment:
2 x ASA 5540s (at two different data centers) configured as a VPN Load Balancing Cluster
Both ASAs are at version 8.4(5)6
IPSec VPN Client version: 5.0.07.440 (64-bit)
Jabber for Windows v9.7.0 build 18474
Issue:
If I am an IPSec VPN user…
I can use Jabber to another IPSec VPN user that is connected to the same ASA appliance.
I can’t use Jabber to another IPSec VPN user that is connected to the different ASA appliance that I am connected to.
In the hub-and-spoke design, where the VPN ASA is a hub, and the VPN client is a spoke; if you have two hubs clustered together, how does one spoke communicate with another spoke on the other hub in the cluster? (How to allow hairpinning to the other ASA)

Portu,
Thanks for your quick reply.
Unfortunately, I do not have access to the ASA logs nor would I be permitted to turn on the debug settings asked for above. I might be able to get the logs but it will take awhile and I suspect they wouldn't be helpful as this ASA supports thousands of clients, therefore, separating out my connection attempts from other clients would be difficult.
I can, though, do whatever you want on the Linux router. Looking over the firewall logs at the time of this problem, I don't see anything that looks suspicious such as dropped packets destined for the Windows client.
As I said in my original post, I'm not a networking expert - by any means - but I am willing to try anything to resolve this. (But I might need a bit of handholding if I need to set up a wireshark andor tcpdump.)
Thanks again.

Suddenly our windows 7 clients can't connect to our wireless network due to a cert error?

Our company uses a Ruckus setup for our wireless network. The laptops have to have a certificate on them issued from our CA and be a member of AD group. Yesterday we noticed that nobody could connect to the internal wireless network. In
the security logs for the computers there is a this error:
A request was made to authenticate to a wireless network.
Subject:
   Security ID:        host/xxx-xxxxxxx
   Account Name:       -
   Account Domain:       -
   Logon ID:       0x0
Network Information:
   Name (SSID):       Forest River Internal
   Interface GUID:       {53b8a5f4-e910-4e3e-ab88-eb4f46356e1f}
   Local MAC Address:   68:94:23:00:26:1F
   Peer MAC Address:   C4:01:7C:4A:88:58
Additional Information:
   Reason Code:       Explicit Eap failure received (0x50005)
   Error Code:       0x80420202
   EAP Reason Code:   0x80420202
   EAP Root Cause String:   The authentication failed because certificate required for this network has expired on the server computer
   EAP Error Code:       0x80420202
this cert was is supposed to be good for another year, is there anyway that I can get the CA server to renew this cert or do I need to issue a new one and distribute it? The other issue I'm running into is I can't seem to get my CA to issue a new computer
cert. All the servers are 08 R2 boxes.

Hi,
Do you have any progresses on this issue by now?
Here is a related KB article below:
Windows 7 does not connect to an IEEE 802.1X-authenticated network if an invalid certificate is installed
http://support.microsoft.com/kb/2494172
Best Regards,
Amy Wang

Windows and Phanter can't connect to Tiger

Hi all, i've got:
Windows XP Service pack 2
Mac mini G4 1,2ghz under Tiger 10.4.6
Mac G4 AGP 400mhz under Phanter 10.3.9
The thing is that when i try to connect from the windows or phanther machine it sais that the current file or direction isn't there anymore, or something like that. The thing is that i can't copy or paste any file to the tiger mac. What can i do to fix that??.
Ohh, the other thing is that the mac mini has the printer connected to the USB port and i want to share the printer for the PC (with the g4 works fine), and the same problem happens. Please help
Greeting to everyone
G4 AGP 400mhz, Mac Mini Mac OS X (10.4.6) DVD-RAM USB2, 512 RAM

You don't need to change around the PC's workgroup. If you are running Windows file sharing, you need to let the PC be the boss. It is running its native protocol, so you shouldn't have to mess with the PC. The Macs run Samba, which has always been flaky, those those are the ones you need to work on.
You need to check all these machines and make sure they are using the same workgroup.
Then, share a folder on the PC. Make sure both the Macs can connect to the PC and access its shared files. At this point, you have verified that all the machines can talk to each other.
Now, turn off file sharing on the PC and turn on Windows file sharing on the Mac. Both the other Mac and the PC should be able to access it. If they can't, check your firewall settings. If you still can't get it to work, post another message here and, now that you have narrowed down the problem quite a bit, someone might know how to fix it.

Windows 8/7 can't connect to RDS GW.

Similar Messages

Maybe you are looking for