Microsoft KB Archive/930707: Difference between revisions
(importing KB archive) |
m (Text replacement - "<" to "<") |
||
Line 86: | Line 86: | ||
<p>Pinging <code>ServerName xxx.xxx.xxx.xxx</code> with 32 bytes of date:<br /> | <p>Pinging <code>ServerName xxx.xxx.xxx.xxx</code> with 32 bytes of date:<br /> | ||
Reply from <code>xxx.xxx.xxx.xxx</code>: bytes=32 time | Reply from <code>xxx.xxx.xxx.xxx</code>: bytes=32 time<1ms TTL=128</p> | ||
</div> | </div> |
Latest revision as of 09:32, 21 July 2020
Article ID: 930707
Article Last Modified on 5/4/2007
APPLIES TO
- Microsoft SoftGrid for Terminal Services
- Microsoft SoftGrid for Windows Desktops
SYMPTOMS
When you refresh a Desktop Configuration Server in the Microsoft SoftGrid Client Management Microsoft Management Console (MMC) snap-in, you receive the following error message:
CAUSE
This problem occurs because the SoftGrid Client cannot communicate with the Desktop Configuration Server.
MORE INFORMATION
The Desktop Configuration Server can be specified by the host name, the DNS name, or the IP address of the server or the load-balancing device.
To verify the server, follow these steps:
- In Administrative Tools, open the SoftGrid Client Management MMC snap-in.
- Click Desktop Configuration Servers.
- Right-click the server that reports the error code, and then click Properties.
- Verify that the server is specified in the Host Name box.
If the server is invalid, the refresh operation fails.
If the server is valid, determine whether the client can ping the host name, the DNS name, or the IP address. To do this, follow these steps:- At a command prompt, type ping ServerName, and then press ENTER. For example, type the following command:
ping SGSERVER01
- If the ping operation succeeds, you receive the following mssage:
If the ping is unsuccessful, you receive the following error message:
- At a command prompt, type ping ServerName, and then press ENTER. For example, type the following command:
If the client cannot ping the server, a network-related issue is preventing the client from communicating with the server. You must correct the network-related issue before you can start an application. For more information, contact the network administrator.
Keywords: kbexpertiseinter kbtshoot KB930707