SBS 2008 No Remote Login

Good Afternoon,I am so close to being migrated off of SBS 2008 to full blown systems and Server 2012 R2. I updated and created a couple new GPOs to update Network Printers to a new VM. Shortly after that i started getting errors when trying to RDP to this SBS Box.I went to the Box and was able to login as the local admin plugging straight in. I was able to find a few articles pointing to GPO causing this. So i disabled the new GPOs to try to resolve this. I even managed to get a Maintenance Window last weekend to reboot. No luck at all.I am able to put in my credentials, then i get the Corporate Network Display and i press ok. After this i get an error Stating "The requested operation cannot be completed because the terminal connection is currently busy processing a connect, disconnect, reset, or delete operation."If i do nothing the...
This topic first appeared in the Spiceworks Community

Similar Messages

Connecting remotely to SBS 2008

I've been reading a great many posts concerning similar issues, but none of them, nor responses quite fit the bill.
I'm running SBS 2008 with Remote Web Workplace enabled, etc. All Windows Client computers are able to access the server and networked machines perfectly well from outside the domain. Also, a VPN can be established via a Windows machine to the server and resources can be used remotely, as designed.
My Mac, running Leopard, can access the server using a vpn; that is, it gives me a "connected" message when I supply correct credentials and the IP of the internet domain name of the server. However, I am unable to access any network resources, nor can I use the Remote Desktop Connection for Mac provided by Microsoft.
The Remote Desktop app will attempt to connect but will issue a prompt to me that the connection was ended at the server end, or it will claim address does not exist. These are local domain addresses, as I am supposedly linked to the domain via VPN, but I'm making that up . . . However, if I am not linked to the vpn and utilize the internet domain name, the same thing occurs.
If I am connected to the vpn, I cannot access any network resources using the "connect to server/folder" procedure described in the literature. "Folder cannot be found" is the consequence of above.
Of interest, the Remote Web Workplace can be accessed using Safari and server address above, but, of course, one cannot remote connect to any computer on the network because of lack of ActiveX stuff.
Any ideas out there?

The solution to above problem lay in the certificate. What the error messages were trying to tell me was the certificate was not "pointing" to the correct location: ie, the internet domain name of the local resource had to be added to the certificate as a new preference. SBS 2008 will disconnect any user without a certificate specifically from the server, and the Keychain needed be directed to supply the correct cert when required.
So the process: download certificate from Server/Downloads; drop into Keychain and change trust settings to "trust"; go to File/New Certificate Preferences and select above certificate and enter correct internet domain name for server; go to System Preferences/Network and add a VPN connection (PPP); enter correct user account and authentication password for server; in ADVANCED, enter correct address for DNS server (usually same as server IP) and Search Domain (the internal domain name of server); connect to VPN, and once connected, go to top menu (Finder) and select Go/Connect to Server and enter smb://server name

Shutdown SBS 2008 blindly

Twice already when I access our SBS 2008 server via RWW the server screen turns remotely and on location blank. On location I get the logon screen. But after login I get a blank screen. Besides the blank screen, the server appears to work normally. The only
way that I can resolve this problem is by rebooting the server. But because I have a blank screen, despite potential negative consequences, I must turn the computer off and on again.
Does anyone know how to shut down or reboot a SBS 2008 server blindly?
Maybe sequence using keyboard combinations?
Thanks

The black screen sounds familiar. I will look for that in a few minutes. But can you open a second browser window on the remote computer and RWW to a desktop, then from an admin level command prompt try to issue the command:
Shutdown /r /t xx /m \\sbs-server-name
Where xx is the number of seconds you want it to wait?
Or could someone on site who knows admin level credentials issue the command from an admin level prompt on their station?
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Server 2012 std not able to see Domain, DC and DNS on Win SBS 2008 std Domain

Hi There
I have a HP ML 110 G5 SBS 2008 std server as my DC on my network. I recently added a HP Microserver running Server 2012 std (with no roles or features installed) to act solely as a file server for a 3rd party program as the program was not running efficiently
on the main server.
The problem I am having now is that the 2012 server keeps falling off the domain and cannot contact DNS server. I have also had to re-enable remote desktop several times. It also shows the 2012 Server as being on a private firewall profile and not on the
domain firewall profile but I suspect that this is part of the same problem.
the resulting problem that this is causing is that the local machines that need to contact an SQL database on the 2012 fileserver intermittently either time out or are very slow to connect.
So far I have tried:
Switching from Static IP to DHCP.
Re-adding the server to the domain.
Stopping and restarting DNS services on the DC.
Checking physical Network connections and routing.
Putting the 2012 server into the same Organizational Unit as the 2008 DC.
Has anyone else encountered this problem when adding a 2012 server to a 2008 domain? I have a feeling that the solution is probably something simple that I've overlooked, but I can't think what. Any help would be greatly appreciated.
Regards
Russ
Also, as some additional info -
Event viewer gives the following errors:
Group Policy Error:
Log Name: System
Source: Microsoft-Windows-GroupPolicy
Date: 2015-04-27 01:17:51 PM
Event ID: 1129
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: [SERVERNAME].[DOMAIN].local
Description:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has
successfully processed. If you do not see a success message for several hours, then contact your administrator.
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
<EventID>1129</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-04-27T11:17:51.111942100Z" />
<EventRecordID>19056</EventRecordID>
<Correlation ActivityID="{C0CBAF2B-1E93-49C0-B910-069AE43F74B2}" />
<Execution ProcessID="732" ThreadID="1336" />
<Channel>System</Channel>
<Computer>[SERVERNAME].[DOMAIN].local</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SupportInfo1">1</Data>
<Data Name="SupportInfo2">1548</Data>
<Data Name="ProcessingMode">0</Data>
<Data Name="ProcessingTimeInMilliseconds">0</Data>
<Data Name="ErrorCode">1222</Data>
<Data Name="ErrorDescription">The network is not present or not started. </Data>
</EventData>
</Event>
DNS Error:
Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 2015-04-27 04:54:58 PM
Event ID: 8015
Task Category: (1028)
Level: Warning
Keywords:
User: NETWORK SERVICE
Computer: [SERVERNAME].[DOMAIN].local
Description:
The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings:
Adapter Name : {3DDD0E46-D879-48C0-9DF6-5FAC0F1A56C4}
Host Name : [SERVERNAME]
Primary Domain Suffix : [DOMAIN].local
DNS server list :
192.168.2.10
Sent update to server : <?>
IP Address(es) :
192.168.2.15
The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running
at this time. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
<EventID>8015</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1028</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2015-04-27T14:54:58.599130300Z" />
<EventRecordID>19105</EventRecordID>
<Correlation />
<Execution ProcessID="856" ThreadID="952" />
<Channel>System</Channel>
<Computer>[SERVERNAME].[DOMAIN].local</Computer>
<Security UserID="S-1-5-20" />
</System>
<EventData>
<Data Name="AdapterName">{3DDD0E46-D879-48C0-9DF6-5FAC0F1A56C4}</Data>
<Data Name="HostName">[SERVERNAME]</Data>
<Data Name="AdapterSuffixName">[DOMAIN].local</Data>
<Data Name="DnsServerList"> 192.168.2.10</Data>
<Data Name="Sent UpdateServer"><?></Data>
<Data Name="Ipaddress">192.168.2.15</Data>
<Data Name="ErrorCode">1460</Data>
</EventData>
</Event>

Can you post an ipconfig /all from the server and the DC?
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

How can I edit the way autodiscover.xml behaves in SBS 2008 and 2011?

I have autodiscover working correctly on a few SBS 2008 and SBS 2011 servers. But, its doing its usual misbehaving. When setting up a new Outlook profile, the user enters their email address and password. Autodiscover is successful in creating all
the account settings, but at the end of the wizard a username and password window pops up with the users full email address incorrectly filled in as the username, which is why it didn't work.
This has always been so annoying about SBS. The user then has to be told to delete their email address in the username field, then fill in "domain\username" instead. Only then is the authentication successful.
I've read lots about people adding the external domain UPN Suffix to ADD&T, then manually changing ever users login to domain.com instead of domain.local.   Then you have to mess with the owa authentication settings in exchange to accept the
UPN.   Its all too ridiculous. There must be a simpler way.
I have read about how you can control how the autodiscover.xml behaves, and there are examples of how to do it in this document:
https://docs.google.com/viewer?a=v&q=cache:0jap1FNKgV0J:https://support.quest.com/Shared/Images/SOL51188_Outlook%2520Automatic%2520Account%2520Configuration.doc+&hl=pl&gl=pl&pid=bl&srcid=ADGEESjizUeFf-JYaM7ZdfIgUCKMMXtcCl0Y3pknFbuwd64GNHIEP1K8a_mpg2YIEisP6sz5DzbtVtdW4Pc42PE0Kjd6bz-3vXz0iaQm7FKi0AnwgvFG_41ZAkBLWynaJtf8s8xyi_d2&sig=AHIEtbSie1mEHTn8el4DPquNxrpovwknUQ
The document above shows the settings we need to change. It looks like we can add the local domain using DomainName into the autodiscover.xml and this will stop autodiscover reporting that the full email address is required.  So we
should be able to get autodiscover to populate the username pop-up with with "domain\user" automatically.
OK, so my question is, how on earth do I edit these settings in SBS 2011? I can't find any articles that talk about how to edit autodiscover.
If I could just edit this one setting (that Microsoft should have correctly configured in the first place) autodiscover will work perfectly for all existing users and all future users, without having to do anything.

Just to straighten out a few things;
1) This is NOT a bug, rather by design. Not every active directory has an exchange server in place, and MS is assuming you don't want to give your internal domain name out to people (which is why it doesn't default to domain\username)
2) Going on what I said in 1), this is NOT SBS specific this is the same way with every Active Directory/Exchange install, keep in mind Microsoft did NOT specially design the software for SBS, they just bundled it into a supported configuration in a neat
little package -since the Exchange server we run on SBS is the same Exchange server powering hundreds of hosted email providers -it makes sense why autodiscover doesn't provide the domain\username (imagine what a mess that would be!)
3) I understand it's a little bit time consuming but it can actually be done for all users in a matter of seconds, select all users, right click and go to Properties, you can then choose the UPN Suffix for all users. When a new user gets created one of the
settings in the wizard is the UPN suffix and is easily changeable as long as you notate for the person creating the user to do it. (The problem here is if you're using the SBS Console instead of AD to setup the User in which case that's just an oversight
in design not a bug in the programming)
4) You can most certainly have a powershell script that changes the UPN suffix from A to B, let me know if you're interested I'll dig one up for you. That can be run on a scheduled task and will solve the remaining issues you have :)
I do see you mentioned it in number 3, I must have missed since I didn't re-read the OP before posting the article, however I just tested on several SBS 2011 machines and OWA authentication settings don't have to be changed at all, this worked immediately
for Outlook Anywhere and Outlook Web Access in my lab and two different customer production systems.
-GreenlightTech

Problem connecting to MS Exchange 2007 on SBS 2008

I am having problems connecting to Exchange via cfexchangeconnection. Our ColdFusion environment is CF9 Enterprise on Win 2008, and the Exchange host is Win SBS 2008 (which uses IIS7).
After having worked through the documentation and following all procedures outlined at
http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec14f31 -7fed.html
plus googling intensively, we have the following method to test the connection
<cfexchangeconnection action="open"
         connection="thisExchangeConnection"
         server="portal.mydomain.com"
         protocol="https"
         formBasedAuthentication="true"
         formBasedAuthenticationURL="https://portal.mydomain.com/owa/auth/owaauth.dll"
         mailboxname="myMailBox"
         username="myUsername"
         password="myPassword" />
<cfdump var="#thisExchangeConnection#">
<cfexchangeconnection action="close"
         connection="thisExchangeConnection" />
The IIS7 implementation in SBS 2008 is quite a lot different to Win 2008, so there are some question marks around some steps in the above documentation. However, we have made sure that:-
1) you can use the credentials above to login via a web browser
2) WebDav is on in IIS
3) there is no IWA and forms based authentication is on
4) certificates are installed correctly on both the CF and Exchange servers
5) the myUsernameaccount has correct permissions in iis/owa/exchange
Despite this, the net result is always
Access to the Exchange server denied.
Ensure that the user name and password are correct.
From research it seems that a lot of people have issues where the underlying problem is actually an Exchange 440 timeout error where the password in the IUSR_<servername> and IWAM_<servername> (IIS/Active Directory) is out of sync.
I was pinning my hopes on the above being the problem but now I find that in SBS 2008 there is no IWAM_<servername> server account.
All this leads me to ask is SBS 2008 actually compatible with the cfexchange tags in CF9? There is nothing in the documentation that I can find that syays that it isn't, but given the amount of time we've spent on what should be straightforward I am wondering if we are on a hiding to nothing. Anyone from Adobe care to comment?
If anyone has managed to get this to work specifically with SBS 2008, or has any advice I'd be grateful to here from you.

Hi,
As said by Sneff , I would also recommend to enable Logging to get more detailed information. Also follow
Configuration of POP/IMAP on SBS 2008 Refer to :
http://blogs.technet.com/b/sbs/archive/2008/09/19/how-to-configure-sbs-2008-to-host-pop3-imap4.aspx
http://blogs.technet.com/b/sbs/archive/2011/08/31/how-to-configure-outlook-for-pop3-imap-and-smtp-connectivity-in-sbs-2008-2011-standard.aspx
As per the error code, you need to follow
http://support.microsoft.com/kb/813514/EN-US
I would also disable AV on both Client machine and TEST , including the Filters of AV.
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Issues After Disabling IPv6 on Your NIC on SBS 2008

If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:
Microsoft Exchange services fail to start
Server hangs at “Applying Computer Settings…” (can eventually logon after 30 – 60 minutes)
Network icons show as offline
Some or all of the following events
Application Log Events
Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185,
“Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Source: MSExchange ADAccess
Event ID: 2601
Task Category: General
Level: Warning
Description:
Process MSEXCHANGEADTOPOLOGY (PID=952). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…>
– Error code=80040a01.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
Source: MSExchange ADAccess
Event ID: 2102
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). All Domain Controller Servers in use are not responding: SBS.sbs2008.local
Source: MSExchange ADAccess
Event ID: 2105
Task Category: Topology
Level: Warning
Description:
Process MAD.EXE (PID=2088). Exchange Active Directory Provider failed to obtain DNS records for domain sbs2008.local. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).
Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=952). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge
Base article 218185, “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
Source: MSExchangeFBPublish
Event ID: 8197
Task Category: General
Level: Error
Description:
Error initializing session for virtual machine SBS. The error number is 0x80040a01. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.
Source: MSExchangeTransportLogSearch
Event ID: 7005
Task Category: General
Level: Error
Description:
Microsoft Exchange couldn’t read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server
localhost did not return a suitable domain controller.
System Log Events
Source: Service Control Manager
Event ID: 7044
Task Category: None
Level: Warning
Description:
The following service is taking more than 16 minutes to start and may have stopped responding: Microsoft Exchange System Attendant
Source: Service Control Manager
Event ID: 7022
Task Category: None
Level: Error
Description:
The Microsoft Exchange Transport service hung on starting.
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Description:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0×0).

Hi,
Based on your description, it seems to be the same as the following blog.
Issues
After Disabling IPv6 on Your NIC on SBS 2008
Did you mean that encounter the same issue? If so, there is a resolution in that blog, please check if can
help you solve the issue.
If any other issue exists or any update, please don’t hesitate to let me know and provide more details. It
will help me understand clearly.
Best regards,
Justin Gu

Excessive downloads by an SBS 2008 client bogging down network

Hello. I have been trying to find the source of a vexing problem on my Small Business 2008 network. It only seems to affect 2 computers and only while logged in. One of them is mine, a Windows 8.1 Pro client computer.
The bottom line is my computer is downloading, continuously from the server at two different levels. One I have lived with for a long time, where I my computer uploads and downloads from the server at 1.5Mbps.
The second, and more concerning, is where it downloads from the server at anywhere from 25-110Mbps. This occurs about 50% of the time. I run NetSpeed Monitor so I can track the traffic. This morning alone, it has downloaded over 320GB from
the server and we have a very small server with only 3 GB on the data drive. This is not a problem on most other stations in the network. Only 1 other computer, a laptop, has a similar problem on this scale and I leave it logged off for now.
I can't find any sign of malware on my client computer and scan regularly (with Kaspersky Small Office Security 3).
All of this network traffic is found under one process in both the client computer and the server, System PID 4. I can provide screen shots if it will help.
Our network performance with the SBS 2008 file server is poor and I think this is contributing.
Please let me know what additional information I can provide to help solve this problem. I tried Process Explorer, but that provided no useful info. I'm wondering if it's a rogue service.
The problem is not evident when I first login, but it appears within a few minutes.
Thank you for any suggestions to try,
Mike

I'm mostly getting these from WireShark:
258117
25.038883000
192.168.11.5
192.168.11.31
TCP
1514
[TCP segment of a reassembled PDU]
Source Port: 445 (445)
Destination Port: 54628 (54628)
(Hundreds of thousands of these per minute). 192.168.11.5 is the server and 192.168.11.31 is my workstation.

The connection was denied because the user account is not authorized for remote login

Using Terminal Server 2008 not able to get non administrator users to login to the remote desktop. Have tried from Windows server 2008 and from Windows servers 2003. Get error login in "The connection was denied because the user account is not authorized for remote login" from Windows Server 2008. Error "The requested session access is denied" from Windows Server 2000.

Is that seriously the only way to do this? Doesn't this render the "Allow log on through Terminal Services" GP Setting useless?
I would like to know this answer, as well. I have created a new AD group for my assistant admins called "Domain Admins (limited)". I have added this group to the GP setting "Allow log on through Terminal Services", but the
assistant admins cannot log in through RDP. It 'feels like' this is all I would need to do.
Craig
Found some good info
here. There are really two things required for a user to connect to a server via RDP. You can configure one of them via Group Policy but not the other.
1) Allow log on through Terminal Services can be configured through Group Policy, no problem.
2) Permissions on the RDP-listener must also be granted. If your user is a member of the local Administrators group or the local Remote Desktop Users group then this is handled. If you are trying to utilize a new, custom group (as I am),
then there isn't a way to do this via group policy (that I have found).
EDIT: Found the answer. I am creating a blog post to outline the steps. They aren't hard, but they're not self-explanatory. It deals with the Restricted Groups mentioned above, but it's still automate-able using Group Policy so that you
don't have to touch each computer. I think the above poster (Andrey Ganev) got it right, but
I had trouble deciphering his instructions.
Here is my blog post that walks through this entire process, step-by-step.

SBS 2008 - 'Sites' Certificate Expired - How to find out where/service it's used - if at all

Greetings,
Is there a way to see what options or services might be using the default sites certificate on our sbs 2008 server?
PowerShell or Certificates MMC add-in?
We have a Go Daddy for email and remote - so I'm thinking this self-signed- expired certificate can be deleted.
Thank you
Thanks in advance

Hi,
As far as I know, we could only use Certificates console check the certificates for the logged on user, for the specific service account and for the specific computer account. It’s hard to
verify which option needs a specific certificate.
For details about Certificates Console, please refer to the following article.
Certificates Console
http://technet.microsoft.com/en-us/library/cc962086.aspx
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

Lost remote login ability

Hi all, hope I can keep this brief and get some help. I set up SBS 2011 and ES 2010 for a small business with a few users, all went well. I had to purchase an SSL certificate to get ES working as I wanted, with remote users of iPads, laptops etc ... and
again, this went as it should. However, since installing the certificate, I have lost the ability to connect to the server remotely. I used to connect via RDP to remote.xxx.co.uk using remote web access feature; but since the certificate I installed was issued
to mail.xxx.co.uk the RDP no longer works. Accessing individual exchange accounts via OWA still work fine, and the ES still works fine. It's just that I'd like to be able to get to the server remotely, so I don't have to visit the site when anything needs
changing. Anyone any ideas? Any input much appreciated, thanks.

Hi,
Based on your description, I understand that you can't remote login server via RWA. Would you please let me know any error message that you can find, when you want to logon remotely? Meanwhile, would you please let me know how you install the third-party
SSL certificate on server?
In addition, please refer to the following KB and run SBS 2011 BPA tool. Please solve issues that SBS BPA can find, then check if this issue still persists.
Windows SBS Best Practices Analyzer (BPA)
http://support.microsoft.com/kb/2673284/en-us
Hope this helps.
Best regards,
Justin Gu

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

Intermittent Disconnects for clients of 2008 R2 Remote Desktop Services

Hello, I have an issue that I am trying to work on for a client who is experiencing intermittent disconnected sessions when logged into a Windows 2008 R2 Remote Desktop Services (RDS) server.
As I mentioned, the disconnect is intermittent in nature and almost appears to be network related, although I cannot find any data in the Application, System, or application specific logs to support that.
The RDS server overall does not exhibit any error, but the user's session is briefly interrupted and then restored. I would like to be able to gain some additional information about what is going on under the hood, but I am having trouble finding any
details on how to turn on debug logging for Terminal Services (er, RDS) on 2008 R2.
Can someone provide some additional details on what kind of logging or other means that I can take on this server in order to gain some additional insight?
Thanks in advance for any advice.

Hi,
There are certain reason for which the client get disconnect from the server. The following are some of the commonly seen symptoms:
• You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session.
• You may have a port assignment conflict.
• You may have an incorrectly-configured Authentication and Encryption setting.
• You may have a certificate corruption.
More information.
http://support.microsoft.com/kb/2477176
If you want to have log for login\logoff for the client on server end then you can get the information from below log.
Event Viewer>Application and Service Logs>Microsoft>Windows>TerminalServices-LocalSessionManager>Operational
Hope it helps!
Thanks.
Dharmesh Solanki
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]

Revoked Certificate on Outlook 2010/Exchange 2007/SBS 2008

Hi All,
I have an issue that has been frustrating me for quite some time now.
Our setup is SBS 2008 with Exchange 2007. 2 Weeks ago we had to renew our certificate for remote.xxxxxxx.com. This was done through the SBS consoles > Network > Fix my Network and followed the wizard. and this worked fine.
I have however got one user who has a problem and he informs me that this is been an issue since before the cert was renewed.
He is a remote laptop user who visits the office maybe 5 times a month. When launching Outlook 2010 on his machine (Win 7 x64) it comes up with the error: Security Alert, Information you exchange with this site cannot be viewed or changed by others. However,
there is a problem with the Site's security certificate. (Red X) The security certificate for this site has been revoked. This site should not be trusted. Then OK and View Certificate buttons.
I have tried to use the View Certificate to install the certificate to the correct store but no luck. Also tried exporting the cert from the server and installing manually into Trusted Root CA, via MMC Certificates Snap-In and no luck.
I'd like to mention that If i log into a different user, on the same domain, on the same laptop, the issue is gone. So it's local to his profile on the laptop.
Plus, he cannot access the OWA on his laptop either, but again a different user - same laptop can. I have verified that the OWA is still working from another machine in the business, that is using the same certificate. I cannot understand why the
subject machine thinks the certificate has been revoked when I don't believe it has.
Can anybody please shed some light on this situation for me - any avenues to explore would be hugely appreciated.
Many thanks
Nicky

I hope this helps
http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/managing-exchange-certificates-part2.html
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Keychain not updated for Remote Login

Since installing Lion on both machines: When I connect to my G5 Powermac from my MBAir, I use the Keychain to remember my password. This feature worked in previous OS Versions by selecting the 'Remember' Option in the dialogue (meaning you would only see the following dialogue when your password changed on the destionation machine).
With Lion, the Password onthe Keychain is not updated when the flag is set. As a result, when I select the destination machine from the Finder, I always have to wait for 'Not Connected' message (while the process tries to log in with my old password). Then, I have to 'Connect As. ..." and enter my current password (every rassafrassin' time).
Can someone please patch this thing.
Thanks,
g

I'm having some trouble with an RD server Win 2008 on a domain. I have a group called domain\authorizedpeople that I would like to enable remote access for. I added this group to the gpo: Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Allow log on through Terminal Services. I also added this group to server manager > configure remote desktop on the server itself, and I added this group to the remote desktop users' group on the server for good measure.
When I try to log on using an account in that group, I get "The connection was denied because the user account is not authorized for remote login". However when I go to server manager > configure remote desktop and add that specific user, it works fine.
Is there a reasonable explanation for this? I really don't want to have to add...
This topic first appeared in the Spiceworks Community

SBS 2008 No Remote Login

Similar Messages

Maybe you are looking for