Remote Web Workplace - Gray Screen

When I log into my client's network, I can Connect To Client Desktops just
fine, but when I Connect To the Server Desktop, all I get is a grey screen.

If I remotely log into my SBS 2003 network, I don't have the same problem.
I can't find any settings that vary between the two. What could be the
problem with my client's Server Desktop?

Hi,

Thanks for your posting!

From your description, I understand that you cannot logon the server by
RWW. If I'm off base, please let me know.

Before we start, please help me collect the following information to
isolate the issue:

1. After you connect to the Server Desktop, did you see the logon widow
which asked you to fill in the username, password and domain name? (Does
the gray screen display after or before logon?)

2. Are there any event log related to this issue?

3. When you connect to the Server Desktop, are there any error messages?

4. Is the client PC on the same LAN with the server? If not, test in the
LAN.

5. Can you logon the server correctly by directly run remote desktop on the
client?

6. You have mentioned that "If I remotely log into my SBS 2003 network, I
don't have the same problem." How do you log on the server remotely?

7. Does this issue happen on all other client PC?

8. Reboot the server, will this problem occur again?

Please capture a screen shoot of the gray screen and post to the newsgroup

If you have any concern on this thread, I am glad to be of further
assistance. We look forward to hearing from you.

Best regards,

Jerry Zhao (MSFT)

Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jerry -

Sorry for the delay - somehow I didn't get notified of your response.

I'll try to answer your questions as well as I can...

Well, that was interesting... In the process of answering your questions, I
let the gray screen sit there, and after 75 seconds (I timed it the second
time), the screen changed to blue and displayed the login window. I then
could log in and was able to administer the server remotely. Guess I just
wasn't patient enough - and when I remotely log into my Windows SBS 2003 - I
don't experience the gray screen delay. I could repeat this several times.

Very strange. If you have any idea what might be causing this, I'd
appreciate hearing about it.

jc



"Jerry zhao (MSFT)" wrote:

> Hi,
>
> Thanks for your posting!
>
> From your description, I understand that you cannot logon the server by
> RWW. If I'm off base, please let me know.
>
> Before we start, please help me collect the following information to
> isolate the issue:
>
> 1. After you connect to the Server Desktop, did you see the logon widow
> which asked you to fill in the username, password and domain name? (Does
> the gray screen display after or before logon?)
>
> 2. Are there any event log related to this issue?
>
> 3. When you connect to the Server Desktop, are there any error messages?
>
> 4. Is the client PC on the same LAN with the server? If not, test in the
> LAN.
>
> 5. Can you logon the server correctly by directly run remote desktop on the
> client?
>
> 6. You have mentioned that "If I remotely log into my SBS 2003 network, I
> don't have the same problem." How do you log on the server remotely?
>
> 7. Does this issue happen on all other client PC?
>
> 8. Reboot the server, will this problem occur again?
>
> Please capture a screen shoot of the gray screen and post to the newsgroup
>
> If you have any concern on this thread, I am glad to be of further
> assistance. We look forward to hearing from you.
>
> Best regards,
>
> Jerry Zhao (MSFT)
>
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hi,

Thanks for your posting back.

This issue may occur because the RWW will go through all your servers to
determine their capabilities (TS support for example). If one is showing in
active directory but it cannot be contacted then the RWW will take
additional time.

As for this point, please check the Client Computers and Server Computers
node in the Server Management console, if there are computers object in it,
but the computer does not exist in your network any longer, please delete
it.

If there is anything else that I can do for you, please feel free to
contact me, and I will be happy to help!

Best regards,

Jerry Zhao (MSFT)

Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Hmmm. There is one client computer listed that has been taken out of
service, but no additional servers. I'll have to wait until I get on-sight
to find which of theclients is gone - they're pre-Windows 2000, so I can't
log on to them remotely.

jc

"Jerry zhao (MSFT)" wrote:

> Hi,
>
> Thanks for your posting back.
>
> This issue may occur because the RWW will go through all your servers to
> determine their capabilities (TS support for example). If one is showing in
> active directory but it cannot be contacted then the RWW will take
> additional time.
>
> As for this point, please check the Client Computers and Server Computers
> node in the Server Management console, if there are computers object in it,
> but the computer does not exist in your network any longer, please delete
> it.
>
> If there is anything else that I can do for you, please feel free to
> contact me, and I will be happy to help!
>
> Best regards,
>
> Jerry Zhao (MSFT)
>
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>

Hi,

Thanks for your kind response and I'm glad to hear that you have found the
root of the issue.

I am here waiting for your good new of solving the problem.

As always, please do post back here again if anything we can still be help.

Best regards,

Jerry Zhao (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.