Link to home
Start Free TrialLog in
Avatar of First Last
First LastFlag for United States of America

asked on

Cant access Vcenter Server HTTP site from Server 2012

I have an odd problem with access to vcenter.  I recently installed Server 2012 for use as a file server and another just today as a test for Citrix.  While attempting to setup Citrix I couldn't contact Vcenter to complete the install.  I tried browsing to https://vcenterserver and the page just times out.  Its accessible from other servers and desktops on the LAN with no issue.  I tried it on my other 2012 server and found the same problem, page times out.  IE Enhanced Security is disabled and UAC is disabled on both servers.  I can ping the address.  2012 runs IE10 but I can access vcenter from other machines using IE10/Win7.

Strange one, any ideas?
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

can you telnet to port 443 ?

Firewall enabled, try disabling firewall.
I've had similar issues with 8/2012.  Try another browser.  If that works then it's an IE issue.  If not then it's a firewall issue or at least not IE.
Avatar of First Last

ASKER

Firewall is disabled (also tried enabling it) and have also tried Chrome and Firefox with the same result.  I can connect to the individual ESX hosts via https but not the vcenter server.  I'm not able to telnet to port 443 on the vcenter server from any device.
Have you tried safe mode with networking?  Maybe something in your A/V is causing an issue?
I would check for firmware & driver updates for the NIC also with such a strange issue.
No AV agent is running on the new instance and they are all virtual running in vcenter so the NIC drivers are the latest.  I'll try safe mode and see what happens.
No dice, also does not work in safe mode.  This is so strange...
You are having a problem accessing from YOUR workstation? Did you install anything Citrix-related on your workstation? What it sounds like is you may have a port 443 conflict. If you can get to https://vcenter from other servers/workstations, then you have some port conflict (seemingly) from where you're trying to access your vcenter from. Citrix uses 443 for some of its services.

~coolsport00
See what is utilizing port 443 by opening a CMD prompt and typing netstat -a

~coolsport00
Hi coolsport00 - No, this is not from my workstation.  I've setup an instance of Server 2012 to test XenDesktop7.  I also have another instance of 2012 which has been in place for a while acting as our file server (Citrix is not installed here).  Part of the XenDesktop install required a HTTP connection to the vcenter server, like this:  https://vcenterserver/sdk.  I found this wasn't working so I attempted to bring up Vcenter's web interface on the 2012 test server and the page fails to load.  On a hunch I tried it from the other 2012 production file server and found the same problem.  It works fine from other machines including my Win7 Pro workstation running IE10.

Running netstat -a returned no port 443 instances in use on either 2012 server.  The Vcenter server shows quite a few connections from various machines which is normal.

I've disabled all the common security related issues (firewall, UAC, IE Enhanced security, added as trusted site etc) but the problem persists.  I'm not finding much on general searches so it does not appear to be a common problem.
Ok, so it is limited to just Win2012? That doesn't surprise me. I won't even begin to go on a soapbox of how much I *DESPISE* 2012/8 :) (or did I just do that??) haha

~coolsport00
Yeah, I've been reading about it all afternoon.  I'm still ambivalent about 2012...it has some cool features but you really need the whole environment to be on the latest and greatest to take advantage.  So far no one I know has deployed Win8/2012.
Just one thing the Citrix installation used too go foobar with the original self signed VMware SSL cert.
Right, I saw references to that in versions prior to XenDesktop7 and Vcenter 5.1 but with the versions I'm running that shouldn't be the case.

An interesting thing happened at the end of the day yesterday.  I installed 2012 R2 as another test and sure enough it works fine on that OS.  I was also able to duplicate the issue on Windows 8 Enterprise.
2012 now has an R2 version? Wow... didn't think it had been out long enough to have such a release...
Yeah, I tested again this morning joined to the domain and getting all my regular group policies...still works.  I thought it was an IE11 thing but that still won't work on Win8.1 Ent with IE11 running.  I'm stumped.
@coolsport00, yes, as well as Windows 8.1 next week, because they are so buggy!

and another version of SCVMM 2012 R2, because SP1 had to be created to work with Windows 2012, because SCVMM 2012 didn't work, and now because SP1 was so crud, we've got SCVMM 2012 R2...bring back Bill!!

and have you used a Surface RT or Surface Pro, so bad, they have to create a new one Surface Pro 2......
@hanccocka - no.. no surface use...and don't want to! I *DESPISE* the GUI MS designed. It's horrendous! I have no desire to either. I won a iPad Mini via Twitter from @Shi_Intl during EMCWorld. Funny thing is, I didn't even have the opportunity to go to that conference, yet still won. I'm not a 'fruit' person per sè, but hey... it's free, & 64GB! WOOT! :)
ASKER CERTIFIED SOLUTION
Avatar of First Last
First Last
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
@danbrown1888 - can you post the specific "routing solution" you did, just so others who might experience this can search here on EE & get an explicit resolution?

Glad you figured it out & sorry we weren't more help.

Regards,
~coolsport00
Sure, it was a simple access control list that prevented access from any machines not authorized to connect to vCenter.  What threw me off is that access was working from VMs on one of my three ESX hosts...I figured my Cisco admin had disabled that for all the hosts but that wasn't the case.
Found own solution