jsarinana
asked on
Remote Web Access SBS 2011 taking a long time to log in
Our Remote Web Access takes almost 2 minutes to log into. After you are it things work just fine
this is on a SBS2011 dual CPL with 32GB ram and 10k RPM drives. the server runs great and users on the LAN do not complain on the file sharing speed. but when you try to log in remotely the log in can take 2 minutes. they have a dedicated 6MB connection
I can go to other companies with a lot less brandwidth and their SBS2011 RWA takes 2-5 seconds to log in.
Please advise
Thanks
this is on a SBS2011 dual CPL with 32GB ram and 10k RPM drives. the server runs great and users on the LAN do not complain on the file sharing speed. but when you try to log in remotely the log in can take 2 minutes. they have a dedicated 6MB connection
I can go to other companies with a lot less brandwidth and their SBS2011 RWA takes 2-5 seconds to log in.
Please advise
Thanks
If you log out and log right back in does it still take that long?
ASKER
No
it's fine takes around 2-3 seconds
it's fine takes around 2-3 seconds
Then that's ...relatively... Normal. IIS, and specifically ASP.Net takes time to spin up professes, and that's what RWA uses. Once they are running, things will be fast. But I'd nobody logs in for awhile and the server needs the resources for other tasks, those processes get spun down again.
ASKER
Cliff
Is there anyway I can speed up IIS , ASP.NET ?
it's still taking up to 2 minutes. Maybe I need to check/fix IIS and asp.NET
Is there anyway I can speed up IIS , ASP.NET ?
it's still taking up to 2 minutes. Maybe I need to check/fix IIS and asp.NET
It isn't broken. It's just how IIS works. Like any server, faster disks, more memory, fewer other programs vying for CPU will help, but it'll always take a little ljger if RWA hasn't been accessed for awhile.
ASKER
Cliff
Thanks for the response but there is something wrong, 2 minutes is way to long
I have 11 other SBS setup this way with more users and less bandwidth. Slowest I've seen was maybe 10 seconds. I'll keep researching. Thanks
Thanks for the response but there is something wrong, 2 minutes is way to long
I have 11 other SBS setup this way with more users and less bandwidth. Slowest I've seen was maybe 10 seconds. I'll keep researching. Thanks
ASKER
Ok
a little more info. Exchange server is not being used, I'm thinking this may why it is taking so log to log in, here are four events I see when I log into RWA
-MSExchange AdAccess event ID: 2154 General
Process w3wp.exe (PID=10228). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.
-MSExchange event ID: 54 task: ADNotifications
The Active Directory system configuration session couldn't be retrieved.
Exception message:
"The Microsoft Exchange Active Directory Topology service on server localhost can't be contacted via RPC. Error 0x6D9.".
-MSExchange RBAC event ID: 22 RBAC
(Process w3wp.exe, PID 10228) "RBAC authorization is unavailable due to the transient error: The Microsoft Exchange Active Directory Topology service on server localhost can't be contacted via RPC. Error 0x6D9."
-SharePoint Foundation event ID: 5586 Database
Unknown SQL Exception -1 occurred. Additional error information from SQL Server is included below.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
a little more info. Exchange server is not being used, I'm thinking this may why it is taking so log to log in, here are four events I see when I log into RWA
-MSExchange AdAccess event ID: 2154 General
Process w3wp.exe (PID=10228). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.
-MSExchange event ID: 54 task: ADNotifications
The Active Directory system configuration session couldn't be retrieved.
Exception message:
"The Microsoft Exchange Active Directory Topology service on server localhost can't be contacted via RPC. Error 0x6D9.".
-MSExchange RBAC event ID: 22 RBAC
(Process w3wp.exe, PID 10228) "RBAC authorization is unavailable due to the transient error: The Microsoft Exchange Active Directory Topology service on server localhost can't be contacted via RPC. Error 0x6D9."
-SharePoint Foundation event ID: 5586 Database
Unknown SQL Exception -1 occurred. Additional error information from SQL Server is included below.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks I will try that