ESX remote console is wary slow, and disconnect...
By Hart - usenet poster
I am using an ESX 2,5, and have serveal virtual windows 2003 servers.
When using MS remote desktop or Dameware everything works just fine.
But when I use the ESX remote console, it is wary slow and disconnects
often. It is almost useless :-(
What is wrong, is it my network connection?
Is it possible to "tune" the ESX remote console?
Any best practices for implementing the remote console?
/C
Solution #1
posted on Aug 01, 2007
Bouncy - usenet poster
Rank:
Apprentice
Rating: 0%, 0 votes
ApprenticeRating: 0%, 0 votes
In this case the link speed & negotiation options don't seem to be a factor.
Everything works the same regardless of whether it is locked down or
allowed to auto-negotiate. Anyway, VNC and Windows Remote Desktop [via RDP]
into any of the guest Win2K3 SP1 servers running under VMware ESX & GSX on
this particular piece of server hardware works properly. It is only the
VMware Virtual Machine Console that has performance problems. If there were
some sort of low-level media problem, I'd expect TCP/IP performance to be
impacted equally for all applications that run over TCP/IP, but that's not
what I'm observing. All guest system console access via VMware Virtual
Machine Console is terribly slow over the LAN and is completely unusable
over the Internet via broadband connections & a T1 pipe at the server end.
All access to the VMware host system seems to function OK, as does file
system access to the guest systems and remote console access via VNC and RDP.
This is was happening with the current build of ESX server, and we then
re-built the server using GSX server and had the same problems. We have
another identical piece of server hardware that's already running GSX server
on top of Win2K and there's not any sort of similar problem there,
although the guest systems are only Win2K & WinXP. It's the newer GSX
server installation on top of Win2K3 SP1 with all Win2K3 SP1 guest systems
that's having the performance problems.
--
Chuck Chopp
ChuckChopp (at) rtfmcsi (dot) com #
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651
"Racing to save lives"
The Leukemia & Lymphoma Society - Team in Training
#
Do not send me unsolicited commercial email.
Everything works the same regardless of whether it is locked down or
allowed to auto-negotiate. Anyway, VNC and Windows Remote Desktop [via RDP]
into any of the guest Win2K3 SP1 servers running under VMware ESX & GSX on
this particular piece of server hardware works properly. It is only the
VMware Virtual Machine Console that has performance problems. If there were
some sort of low-level media problem, I'd expect TCP/IP performance to be
impacted equally for all applications that run over TCP/IP, but that's not
what I'm observing. All guest system console access via VMware Virtual
Machine Console is terribly slow over the LAN and is completely unusable
over the Internet via broadband connections & a T1 pipe at the server end.
All access to the VMware host system seems to function OK, as does file
system access to the guest systems and remote console access via VNC and RDP.
This is was happening with the current build of ESX server, and we then
re-built the server using GSX server and had the same problems. We have
another identical piece of server hardware that's already running GSX server
on top of Win2K and there's not any sort of similar problem there,
although the guest systems are only Win2K & WinXP. It's the newer GSX
server installation on top of Win2K3 SP1 with all Win2K3 SP1 guest systems
that's having the performance problems.
--
Chuck Chopp
ChuckChopp (at) rtfmcsi (dot) com #
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651
"Racing to save lives"
The Leukemia & Lymphoma Society - Team in Training
#
Do not send me unsolicited commercial email.
Was this solution helpful? Show your Appreciation by rating it:
Solution #2
posted on Aug 01, 2007
Gary10 - usenet poster
Rank: Apprentice
Rating: 0%, 0 votes
ApprenticeRating: 0%, 0 votes
We had slightly different problem (could connect to the ESX management
interface via HTTP but Virtual Centre wouldn't connect) but I would
agree with Don about the link speed stuff. The autodetection of line
speed is a common problem I see across a range of OSes. I do most of
my work with HP Proliant servers and Cisco switches but I don't know
if the problem is specific to either or both of these platforms.
I found the following article very helpful. Just one note, the link
speed change didn't seem to take effect on restarting the interface as
detailed in the document, the ESX server needed to be rebooted.
#
interface via HTTP but Virtual Centre wouldn't connect) but I would
agree with Don about the link speed stuff. The autodetection of line
speed is a common problem I see across a range of OSes. I do most of
my work with HP Proliant servers and Cisco switches but I don't know
if the problem is specific to either or both of these platforms.
I found the following article very helpful. Just one note, the link
speed change didn't seem to take effect on restarting the interface as
detailed in the document, the ESX server needed to be rebooted.
#
Was this solution helpful? Show your Appreciation by rating it:
Solution #3
posted on Aug 01, 2007
Pasty - usenet poster
Rank: Apprentice
Rating: 0%, 0 votes
ApprenticeRating: 0%, 0 votes
I had this problem and it was because there was a mismatch between on
network card and the switch. The switch was set to a 100/full my card was
on auto (it was a Gig card). Once the network guys change the switch to
auto the problem went way.
Don
...
network card and the switch. The switch was set to a 100/full my card was
on auto (it was a Gig card). Once the network guys change the switch to
auto the problem went way.
Don
...
Was this solution helpful? Show your Appreciation by rating it:
Solution #4
posted on Aug 01, 2007
Luisa_K - usenet poster
Rank: Apprentice
Rating: 0%, 0 votes
ApprenticeRating: 0%, 0 votes
I've had this problem before with the remote console disconnecting.
- Turned out to the the network card settings for the service console.
You can amend these by logging into the service console and editting
the file /etc/modules.conf.
See -
#
- Turned out to the the network card settings for the service console.
You can amend these by logging into the service console and editting
the file /etc/modules.conf.
See -
#
Was this solution helpful? Show your Appreciation by rating it:
Solution #5
posted on Aug 01, 2007
Grant - usenet poster
Rank: Apprentice
Rating: 0%, 0 votes
ApprenticeRating: 0%, 0 votes
Hi there..
I have had the same problem. The only tweak I have found so far, is to
set "Allow unencrypted VMware Management Interface and Remote Console
sessions" in the MUI.
Not perfect solution at all, but it helps :-)
JF@DK
C skrev:
I have had the same problem. The only tweak I have found so far, is to
set "Allow unencrypted VMware Management Interface and Remote Console
sessions" in the MUI.
Not perfect solution at all, but it helps :-)
JF@DK
C skrev:
Was this solution helpful? Show your Appreciation by rating it:
Solution #6
posted on Aug 01, 2007
herself - usenet poster
Rank: Apprentice
Rating: 0%, 0 votes
ApprenticeRating: 0%, 0 votes
I've had the exact same problem with the VMware Virtual Machine Console,
both with ESX v2.5 and with GSX v3.2 when running Win2K3 guests. The
virtual console is so slow - mouse movement lags - keystrokes are "delayed"
- that it is almost unusable via a LAN connection [1 gigabit ethernet], and
via the Internet [thru the firewall, over a DSL connection], it is
completely unusable.
I posted about this on the GSX server news group and still haven't received
any sort of meaningful responses.
--
Chuck Chopp
ChuckChopp (at) rtfmcsi (dot) com #
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651
"Racing to save lives"
The Leukemia & Lymphoma Society - Team in Training
#
Do not send me unsolicited commercial email.
both with ESX v2.5 and with GSX v3.2 when running Win2K3 guests. The
virtual console is so slow - mouse movement lags - keystrokes are "delayed"
- that it is almost unusable via a LAN connection [1 gigabit ethernet], and
via the Internet [thru the firewall, over a DSL connection], it is
completely unusable.
I posted about this on the GSX server news group and still haven't received
any sort of meaningful responses.
--
Chuck Chopp
ChuckChopp (at) rtfmcsi (dot) com #
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651
"Racing to save lives"
The Leukemia & Lymphoma Society - Team in Training
#
Do not send me unsolicited commercial email.
Was this solution helpful? Show your Appreciation by rating it:
Suggest a new solution for this problem
Post a New problem for IBM VMware ESX Server for PC, Linux
Email this problem
Post a New problem for IBM VMware ESX Server for PC, Linux
Email this problem
Can you Help with these Network Management Tools problems?
Network Management Tools
drag nat spk med solutions 8
drag nat spk med solutions 8
Vista new computer - message... Answer This...
Repair Service
Find Network Man. Repairman Near You:
FixYa does not evaluate or guarantee the accuracy of any information provided through its proposed solutions,
posts, or Expert Assistance Sessions. By entering this site you declare you read and agreed to its Terms.
You may NOT copy or distribute the content that appears on this site without written
permission from FixYa Inc.
About | News
| Contact
| Find Products
| Find Cars
| Terms
| Privacy Policy
| FAQ
Tags | Blog | Repair Directory | Extended Warranty | Partners | Jobs |
Tags | Blog | Repair Directory | Extended Warranty | Partners | Jobs |