Firewall open ports for vSphere
up vote
2
down vote
favorite
I need to open ports on a firewall, so that a client can access his VM console through vCenter server's Web Client. I had a look at this page about port description, but I am a little confused.
I already have a port open for the client on a firewall, to access vCenter server's 443 port (https), 9443 (for vSphere PC client), 902 (TCP/UDP) and the client still gets some kind of error related to 902 port being blocked.
Do I have to open port 902 on ESXi hosts and not on vCenter instead? What should I permit as well?
networking firewall port vsphere
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
add a comment |
up vote
2
down vote
favorite
I need to open ports on a firewall, so that a client can access his VM console through vCenter server's Web Client. I had a look at this page about port description, but I am a little confused.
I already have a port open for the client on a firewall, to access vCenter server's 443 port (https), 9443 (for vSphere PC client), 902 (TCP/UDP) and the client still gets some kind of error related to 902 port being blocked.
Do I have to open port 902 on ESXi hosts and not on vCenter instead? What should I permit as well?
networking firewall port vsphere
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
1
Unless vCenter is having trouble communicating with the hosts, no. The problem by the sound of it is only between the http client and VC server. What sort of firewall have you got are there logging abilities to confirm it is the firewall?
– Chris
Nov 19 '13 at 11:50
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I need to open ports on a firewall, so that a client can access his VM console through vCenter server's Web Client. I had a look at this page about port description, but I am a little confused.
I already have a port open for the client on a firewall, to access vCenter server's 443 port (https), 9443 (for vSphere PC client), 902 (TCP/UDP) and the client still gets some kind of error related to 902 port being blocked.
Do I have to open port 902 on ESXi hosts and not on vCenter instead? What should I permit as well?
networking firewall port vsphere
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
I need to open ports on a firewall, so that a client can access his VM console through vCenter server's Web Client. I had a look at this page about port description, but I am a little confused.
I already have a port open for the client on a firewall, to access vCenter server's 443 port (https), 9443 (for vSphere PC client), 902 (TCP/UDP) and the client still gets some kind of error related to 902 port being blocked.
Do I have to open port 902 on ESXi hosts and not on vCenter instead? What should I permit as well?
networking firewall port vsphere
networking firewall port vsphere
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
edited Oct 30 '16 at 19:05
Hennes
58.7k792141
58.7k792141
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
asked Nov 19 '13 at 11:41
Ashtray
1,32911216
1,32911216
1
Unless vCenter is having trouble communicating with the hosts, no. The problem by the sound of it is only between the http client and VC server. What sort of firewall have you got are there logging abilities to confirm it is the firewall?
– Chris
Nov 19 '13 at 11:50
add a comment |
1
Unless vCenter is having trouble communicating with the hosts, no. The problem by the sound of it is only between the http client and VC server. What sort of firewall have you got are there logging abilities to confirm it is the firewall?
– Chris
Nov 19 '13 at 11:50
1
1
Unless vCenter is having trouble communicating with the hosts, no. The problem by the sound of it is only between the http client and VC server. What sort of firewall have you got are there logging abilities to confirm it is the firewall?
– Chris
Nov 19 '13 at 11:50
Unless vCenter is having trouble communicating with the hosts, no. The problem by the sound of it is only between the http client and VC server. What sort of firewall have you got are there logging abilities to confirm it is the firewall?
– Chris
Nov 19 '13 at 11:50
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
This link shows that port 902 needs to be open between the vCenter Server (source) and the ESX(i) host (target) in order to be able to make a remote MKS connection, as you suspected.
[If the above link doesn't work, try this.]
edited Dec 4 '13 at 18:22
Scott
15.5k113789
answered Dec 4 '13 at 17:08
jkovba
27915
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
This link shows that port 902 needs to be open between the vCenter Server (source) and the ESX(i) host (target) in order to be able to make a remote MKS connection, as you suspected.
[If the above link doesn't work, try this.]
edited Dec 4 '13 at 18:22
Scott
15.5k113789
answered Dec 4 '13 at 17:08
jkovba
27915
add a comment |
up vote
0
down vote
This link shows that port 902 needs to be open between the vCenter Server (source) and the ESX(i) host (target) in order to be able to make a remote MKS connection, as you suspected.
[If the above link doesn't work, try this.]
edited Dec 4 '13 at 18:22
Scott
15.5k113789
answered Dec 4 '13 at 17:08
jkovba
27915
add a comment |
up vote
0
down vote
up vote
0
down vote
This link shows that port 902 needs to be open between the vCenter Server (source) and the ESX(i) host (target) in order to be able to make a remote MKS connection, as you suspected.
[If the above link doesn't work, try this.]
edited Dec 4 '13 at 18:22
Scott
15.5k113789
answered Dec 4 '13 at 17:08
jkovba
27915
This link shows that port 902 needs to be open between the vCenter Server (source) and the ESX(i) host (target) in order to be able to make a remote MKS connection, as you suspected.
[If the above link doesn't work, try this.]
edited Dec 4 '13 at 18:22
Scott
15.5k113789
answered Dec 4 '13 at 17:08
jkovba
27915
edited Dec 4 '13 at 18:22
Scott
15.5k113789
edited Dec 4 '13 at 18:22
Scott
15.5k113789
edited Dec 4 '13 at 18:22
Scott
15.5k113789
15.5k113789
answered Dec 4 '13 at 17:08
jkovba
27915
answered Dec 4 '13 at 17:08
jkovba
27915
answered Dec 4 '13 at 17:08
jkovba
27915
27915
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f677862%2ffirewall-open-ports-for-vsphere%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Unless vCenter is having trouble communicating with the hosts, no. The problem by the sound of it is only between the http client and VC server. What sort of firewall have you got are there logging abilities to confirm it is the firewall?
– Chris
Nov 19 '13 at 11:50