MiroRakus
Contributor
Contributor

Cannot connect to vmware desktop via thin client

Hello all,

I installed VMware view on two esx servers on cluster. I have a desktop pool.

I have two network card on the desktops. One is connect to the domain controller(dhcp server) and one to the internet (dhcp server).

There is my issue. If i have connection to the domai and to the internet, i can not connect to the desktop via Devon thin clien. (error - Pool is not available, try again or contact admin)

If I disable Internet connection or unpluge cable from network (internet) or all network cards are connect to the domain, I can connect with thin client to the desktops.

Can you please help with this?

Thanks

Miro

0 Kudos
5 Replies
mnasir
Enthusiast
Enthusiast

Do you have 2 network cards in the VMs or in your desktop? if they are in the VMs, then, I am not sure why would you need two network cards on the VMs to access the internet. Would it be possible for you to explain your setup - may be with a diagram?

0 Kudos
mnasir
Enthusiast
Enthusiast

Are you still having the same issue?

0 Kudos
MiroRakus
Contributor
Contributor

Hello,

I have 2 network card in VM and there I have some virtual desktops. I need one connection to the intranet and one to the internet. Thin clients are in intranet network.

0 Kudos
mnasir
Enthusiast
Enthusiast

Okay - are you able to ping your view manager server from you thin clients. If so, you should be able to connect to your VMs without a problem -- Also, is your View Manager Server is also VM - how many network cards you have on your View Manager server? Did you try to add a static route on your VMs and see if that resolves the problem: here's how to add a static route on your windows VM.

Manipulates network routing tables.

ROUTE [command

-f Clears the routing tables of all gateway entries. If this is

used in conjunction with one of the commands, the tables are

cleared prior to running the command.

-p When used with the ADD command, makes a route persistent across

boots of the system. By default, routes are not preserved

when the system is restarted. Ignored for all other commands,

which always affect the appropriate persistent routes. This

option is not supported in Windows 95.

command One of these:

PRINT Prints a route

ADD Adds a route

DELETE Deletes a route

CHANGE Modifies an existing route

destination Specifies the host.

MASK Specifies that the next parameter is the 'netmask' value.

netmask Specifies a subnet mask value for this route entry.

If not specified, it defaults to 255.255.255.255.

gateway Specifies gateway.

interface the interface number for the specified route.

METRIC specifies the metric, ie. cost for the destination.

All symbolic names used for destination are looked up in the network database

file NETWORKS. The symbolic names for gateway are looked up in the host name

database file HOSTS.

If the command is PRINT or DELETE. Destination or gateway can be a wildcard,

(wildcard is specified as a star '*'), or the gateway argument may be omitted.

If Dest contains a * or ?, it is treated as a shell pattern, and only

matching destination routes are printed. The '*' matches any string,

and '?' matches any one char. Examples: 157..1, 157., 127.*, 224.

Diagnostic Notes:

Invalid MASK generates an error, that is when (DEST & MASK) != DEST.

Example> route ADD 157.0.0.0 MASK 155.0.0.0 157.55.80.1 IF 1

The route addition failed: The specified mask parameter is invalid. (Destination & Mask) != Destination.

Examples:

> route PRINT

> route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3 IF 2

destination^ ^mask gateway metric ^

Interface^

If IF is not given, it tries to find the best interface for a given

gateway.

> route PRINT

> route PRINT 157* .... Only prints those matching 157*

> route CHANGE 157.0.0.0 MASK 255.0.0.0 157.55.80.5 METRIC 2 IF 2

CHANGE is used to modify gateway and/or metric only.

> route PRINT

> route DELETE 157.0.0.0

> route PRINT

Please consider awarding points by selecting "Answered" or "helpful", if you find this post useful.Thanks!!

MiroRakus
Contributor
Contributor

Hi,

View Manager Server is VM and I have there two network cards in intranet.

When I logon to view manager server via Thinclient and I see there 2 desktop pool. If Itake one of this, I can not connect to the VMs desktops. I have failure message. Desktop pool is not avalaible, try later or contact administrator.

I am going to setup intranet static IPs.

__________________________________________

Update:

I setup intranet static IPs and it seems it is working now.

Another question:

I setup static IP on WindowsXP, where I have some snapshots. When I want create automatic desktop pool with 20 desktops, I have same IP on all desktops and them I must reset all IP.

Is it possible somewhere setup it automatically?

0 Kudos