• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

EMC and Powershell cant connect - "A Specified Login session does not exist

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2010] >> Management >> EMC and Powershell cant connect - "A Specified Login session does not exist Page: [1]
Login
Message << Older Topic   Newer Topic >>
EMC and Powershell cant connect - "A Specified Log... - 6.Apr.2010 6:42:27 AM   
Krobaruk

 

Posts: 6
Joined: 24.Mar.2010
Status: offline
I setup this exchange server last week and could login fine on Thursday. No reboots since but now I cannot manage the server and get the error below. I thought there might be something wrong with my certs or location of service type settings last week as the message tracking would not work on the local URL, only the public. I have tried setting my signed cert for the public IP in IIS and the self generated cert for the Private IP but this doesnt seem to help.

Does anyone know where I should look to fix this?


VERBOSE: Connecting to hostedexchsvr1.domain.local
[hostedexchsvr1.domain.local] Connecting to remote server failed with the following error message : WinRM cannot pro
cess the request. The following error occured while using Kerberos authentication: A specified logon session does not e
xist. It may already have been terminated.
Possible causes are:
-The user name or password specified are invalid.
-Kerberos is used when no authentication method and no user name are specified.
-Kerberos accepts domain user names, but not local user names.
-The Service Principal Name (SPN) for the remote computer name and port does not exist.
-The client and remote computers are in different domains and there is no trust between the two domains.
After checking for the above issues, try the following:
-Check the Event Viewer for events related to authentication.
-Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or us
e HTTPS transport.
Note that computers in the TrustedHosts list might not be authenticated.
-For more information about WinRM configuration, run the following command: winrm help config. For more information,
see the about_Remote_Troubleshooting Help topic.
  + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
  + FullyQualifiedErrorId : PSSessionOpenFailed

C:\Users\Administrator>winrm get winrm/config/client
Client
   NetworkDelayms = 5000
   URLPrefix = wsman
   AllowUnencrypted = false
   Auth
       Basic = true
       Digest = true
       Kerberos = true
       Negotiate = true
       Certificate = true
       CredSSP = false
   DefaultPorts
       HTTP = 5985
       HTTPS = 5986
   TrustedHosts

C:\Users\Administrator>winrm get winrm/config
Config
   MaxEnvelopeSizekb = 150
   MaxTimeoutms = 60000
   MaxBatchItems = 32000
   MaxProviderRequests = 4294967295
   Client
       NetworkDelayms = 5000
       URLPrefix = wsman
       AllowUnencrypted = false
       Auth
           Basic = true
           Digest = true
           Kerberos = true
           Negotiate = true
           Certificate = true
           CredSSP = false
       DefaultPorts
           HTTP = 5985
           HTTPS = 5986
       TrustedHosts
   Service
       RootSDDL = *REMOVED*
       MaxConcurrentOperations = 4294967295
       MaxConcurrentOperationsPerUser = 15
       EnumerationTimeoutms = 60000
       MaxConnections = 25
       MaxPacketRetrievalTimeSeconds = 120
       AllowUnencrypted = false
       Auth
           Basic = false
           Kerberos = true
           Negotiate = true
           Certificate = false
           CredSSP = false
           CbtHardeningLevel = Relaxed
       DefaultPorts
           HTTP = 5985
           HTTPS = 5986
       IPv4Filter = *
       IPv6Filter = *
       EnableCompatibilityHttpListener = false
       EnableCompatibilityHttpsListener = false
       CertificateThumbprint
   Winrs
       AllowRemoteShellAccess = true
       IdleTimeout = 180000
       MaxConcurrentUsers = 5
       MaxShellRunTime = 2147483647
       MaxProcessesPerShell = 15
       MaxMemoryPerShellMB = 150
       MaxShellsPerUser = 5

< Message edited by Krobaruk -- 6.Apr.2010 6:48:34 AM >
Post #: 1
RE: EMC and Powershell cant connect - "A Specified... - 6.Apr.2010 9:26:56 AM   
Krobaruk

 

Posts: 6
Joined: 24.Mar.2010
Status: offline
*Embarrassed* RDP had changed the default login to local administrator, logged in as domain admin and it worked fine. Thought I'd leave this answer just in case someone else gets the same problem.

(in reply to Krobaruk)
Post #: 2
RE: EMC and Powershell cant connect - "A Specified... - 5.May2011 4:39:23 PM   
screamerz

 

Posts: 1
Joined: 5.May2011
Status: offline
Could you please explain better how you solved?

I get the same error while connecting using Administrator account thru RDP and opening EMC or PS on remote desktop. This doesn't happens when connecting using any other administration users, only with the main Administrator.

It always worked perfectly 'till today

THANK YOU VERY MUCH!

(in reply to Krobaruk)
Post #: 3

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2010] >> Management >> EMC and Powershell cant connect - "A Specified Login session does not exist Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter