windows 2008 R2 rem...
 
Bildirimler
Hepsini Temizle

windows 2008 R2 remote web access  

  RSS
Ercan Ozkurt
(@ErcanOzkurt)
Üye

Merhabalar, 

Windows 2008 R2 üzerinde remote web accesi çalıştırıyorum. Administrator accountu ile giriş yaptığım zaman rdweb üzerinde tüm oluşturduğum uygulamlar geliyor. Fakat normal bir kullanıcı  ile giriş yaptığım zaman hiçbir uygulama görünmüyor. Bu konuda daha önce uygulama yapmış arkadaş var mı acaba.

Alıntı
Gönderildi : 13/06/2011 18:49
CozumPark
(@cozumpark)
Onursal Üye Yönetici

İzinleri kontrol etmen lazım :

http://technet.microsoft.com/en-us/library/cc781509%28WS.10%29.aspx

 

CevapAlıntı
Gönderildi : 13/06/2011 19:04
Yalçin KARACA
(@yalcinkaraca)
Üye

Merhaba Ercan Bey;


 Almış olduğunuz hatanın resmini görebilirmiyim.

CevapAlıntı
Gönderildi : 13/06/2011 19:05
Ercan Ozkurt
(@ErcanOzkurt)
Üye

http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/windows-server-2008-terminal-services-web-access-part1.html  

linkteki 4. resimdeki hata gibi boş ekran geliyor.

 

Yetkileri kontrol ediyorum. Kullanıcı terminal servera remote desktop yapabiliyor. Fakat rdweb ile bağlanıldığında boş ekran getiriyor.  

CevapAlıntı
Gönderildi : 13/06/2011 19:30
Yalçin KARACA
(@yalcinkaraca)
Üye

Ercan Bey;


 Alper Hocamın dediği gibi security ayarlarını kontrol ettinizmi olaygünlügünde hata mesajı varmı.

CevapAlıntı
Gönderildi : 13/06/2011 19:42
Ercan Ozkurt
(@ErcanOzkurt)
Üye

Normal user ile girdiğim zaman security logları altına aşağıdaki şekilde bir kayıt atıyor.

Log Name:      Security

Source:        Microsoft-Windows-Security-Auditing

Date:          13.06.2011 16:54:06

Event ID:      4625

Task Category: Logon

Level:         Information

Keywords:      Audit Failure

User:          N/A

Computer:      terminal

Description:

An account failed to log on.

Subject:

Security ID: IIS APPPOOL\RDWebAccess

Account Name: RDWebAccess

Account Domain: IIS APPPOOL

Logon ID: 0xb851c

Logon Type: 3

Account For Which Logon Failed:

Security ID: NULL SID

Account Name:

Account Domain:

Failure Information:

Failure Reason: Unknown user name or bad password.

Status: 0xc000006d

Sub Status: 0xc0000064

Process Information:

Caller Process ID: 0xe98

Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe

Network Information:

Workstation Name: TERMINAL

Source Network Address: -

Source Port: -

Detailed Authentication Information:

Logon Process: Authz   

Authentication Package: Kerberos

Transited Services: -

Package Name (NTLM only): -

Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.

- Transited services indicate which intermediate services have participated in this logon request.

- Package name indicates which sub-protocol was used among the NTLM protocols.

- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />

    <EventID>4625</EventID>

    <Version>0</Version>

    <Level>0</Level>

    <Task>12544</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8010000000000000</Keywords>

    <TimeCreated SystemTime="2011-06-13T13:54:06.202127000Z" />

    <EventRecordID>4974</EventRecordID>

    <Correlation />

    <Execution ProcessID="488" ThreadID="2904" />

    <Channel>Security</Channel>

    <Computer>terminal.avmnet.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="SubjectUserSid">S-1-5-82-604604840-3341247844-1790606609-4006251754-2470522317</Data>

    <Data Name="SubjectUserName">RDWebAccess</Data>

    <Data Name="SubjectDomainName">IIS APPPOOL</Data>

    <Data Name="SubjectLogonId">0xb851c</Data>

    <Data Name="TargetUserSid">S-1-0-0</Data>

    <Data Name="TargetUserName">

    </Data>

    <Data Name="TargetDomainName">

    </Data>

    <Data Name="Status">0xc000006d</Data>

    <Data Name="FailureReason">%%2313</Data>

    <Data Name="SubStatus">0xc0000064</Data>

    <Data Name="LogonType">3</Data>

    <Data Name="LogonProcessName">Authz   </Data>

    <Data Name="AuthenticationPackageName">Kerberos</Data>

    <Data Name="WorkstationName">TERMINAL</Data>

    <Data Name="TransmittedServices">-</Data>

    <Data Name="LmPackageName">-</Data>

    <Data Name="KeyLength">0</Data>

    <Data Name="ProcessId">0xe98</Data>

    <Data Name="ProcessName">C:\Windows\System32\inetsrv\w3wp.exe</Data>

    <Data Name="IpAddress">-</Data>

    <Data Name="IpPort">-</Data>

  </EventData>

</Event> 

CevapAlıntı
Gönderildi : 13/06/2011 20:02
Ercan Ozkurt
(@ErcanOzkurt)
Üye

Normal user ile girdiğim zaman security logları altına aşağıdaki şekilde bir kayıt atıyor.

Log Name:      Security

Source:        Microsoft-Windows-Security-Auditing

Date:          13.06.2011 16:54:06

Event ID:      4625

Task Category: Logon

Level:         Information

Keywords:      Audit Failure

User:          N/A

Computer:      terminal

Description:

An account failed to log on.

Subject:

Security ID: IIS APPPOOL\RDWebAccess

Account Name: RDWebAccess

Account Domain: IIS APPPOOL

Logon ID: 0xb851c

Logon Type: 3

Account For Which Logon Failed:

Security ID: NULL SID

Account Name:

Account Domain:

Failure Information:

Failure Reason: Unknown user name or bad password.

Status: 0xc000006d

Sub Status: 0xc0000064

Process Information:

Caller Process ID: 0xe98

Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe

Network Information:

Workstation Name: TERMINAL

Source Network Address: -

Source Port: -

Detailed Authentication Information:

Logon Process: Authz   

Authentication Package: Kerberos

Transited Services: -

Package Name (NTLM only): -

Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.

- Transited services indicate which intermediate services have participated in this logon request.

- Package name indicates which sub-protocol was used among the NTLM protocols.

- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />

    <EventID>4625</EventID>

    <Version>0</Version>

    <Level>0</Level>

    <Task>12544</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8010000000000000</Keywords>

    <TimeCreated SystemTime="2011-06-13T13:54:06.202127000Z" />

    <EventRecordID>4974</EventRecordID>

    <Correlation />

    <Execution ProcessID="488" ThreadID="2904" />

    <Channel>Security</Channel>

    <Computer>terminal.avmnet.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="SubjectUserSid">S-1-5-82-604604840-3341247844-1790606609-4006251754-2470522317</Data>

    <Data Name="SubjectUserName">RDWebAccess</Data>

    <Data Name="SubjectDomainName">IIS APPPOOL</Data>

    <Data Name="SubjectLogonId">0xb851c</Data>

    <Data Name="TargetUserSid">S-1-0-0</Data>

    <Data Name="TargetUserName">

    </Data>

    <Data Name="TargetDomainName">

    </Data>

    <Data Name="Status">0xc000006d</Data>

    <Data Name="FailureReason">%%2313</Data>

    <Data Name="SubStatus">0xc0000064</Data>

    <Data Name="LogonType">3</Data>

    <Data Name="LogonProcessName">Authz   </Data>

    <Data Name="AuthenticationPackageName">Kerberos</Data>

    <Data Name="WorkstationName">TERMINAL</Data>

    <Data Name="TransmittedServices">-</Data>

    <Data Name="LmPackageName">-</Data>

    <Data Name="KeyLength">0</Data>

    <Data Name="ProcessId">0xe98</Data>

    <Data Name="ProcessName">C:\Windows\System32\inetsrv\w3wp.exe</Data>

    <Data Name="IpAddress">-</Data>

    <Data Name="IpPort">-</Data>

  </EventData>

</Event> 

 

 

CevapAlıntı
Gönderildi : 13/06/2011 20:03
Ercan Ozkurt
(@ErcanOzkurt)
Üye

Bir fikri olan yok sanırım.

CevapAlıntı
Gönderildi : 14/06/2011 12:31
CozumPark
(@cozumpark)
Onursal Üye Yönetici

http://www.fredmastro.com/post/EventID-4625-on-Windows-2008-IIS7-Windows-Authentication-Error.aspx

Linkteki çözümü dene, fakat yapmadan önce mutlaka yedek al.

CevapAlıntı
Gönderildi : 14/06/2011 12:41
Yalçin KARACA
(@yalcinkaraca)
Üye

I found the solution on the MS Support site, Q89681.  Which suggested to turn off the LoopbackCheck.


To set the DisableLoopbackCheck registry key yourself, follow these steps:



  1. Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

    281308 Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name


  2. Click Start, click Run, type regedit, and then click OK.

  3. In Registry Editor, locate and then click the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa


  4. Right-click Lsa, point to New, and then click DWORD Value.

  5. Type DisableLoopbackCheck, and then press ENTER.

  6. Right-click DisableLoopbackCheck, and then click Modify.

  7. In the Value data box, type 1, and then click OK.

  8. Quit Registry Editor, and then restart your computer.

CevapAlıntı
Gönderildi : 22/07/2011 12:33
Paylaş: