Mixing
Perforce - Windows server 2016 can't connect from client
I am trying to set up my Azure Virtual machine to become a Perforce remote repository server.
First let me take you through the installation of Helix on the server:
And after the install is complete it says:
So far so good now from my client computer (my local desktop) I attempt to connect to this server, however, I get an error:
Now first I thought that the port wasn't open in my inbound so I added the following network rule in my Azure cloud portal:
However, this didn't do anything for me and I get the same error.
So now I am left kinda stranded. Has anyone had this issue and know how i can connect to my remote machine from perforce?
From the comment below when i type p4 info i get the following:
User name: ******
Client name: PerforceServer
Client host: PerforceServer
Client unknown.
Current directory: c:Users*****
Peer address: 127.0.0.1:50413
Client address: 127.0.0.1
Server address: PerforceServer:1666
Server root: C:Users*****VersionControl
Server date: 2018/11/21 14:44:12 +0000 Coordinated Universal Time
Server uptime: 00:01:27
Server version: P4D/NTX64/2018.2/1724420 (2018/11/02)
Server license: none
Case Handling: insensitive
However using the prefix PerforceServer:1666 i still cannot connect
When running netstat:
TCP 127.0.0.1:50688 PerforceServer:1666 TIME_WAIT
TCP 127.0.0.1:50689 PerforceServer:1666 TIME_WAIT
Also if i run p4d i get the following error:
Perforce server error:
Listen 1666 failed.
TCP listen on 1666 failed.
bind: 0.0.0.0:1666: WSAEADDRINUSE
windows
azure perforce helix-server asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
|
show 2 more comments
I am trying to set up my Azure Virtual machine to become a Perforce remote repository server.
First let me take you through the installation of Helix on the server:
And after the install is complete it says:
So far so good now from my client computer (my local desktop) I attempt to connect to this server, however, I get an error:
Now first I thought that the port wasn't open in my inbound so I added the following network rule in my Azure cloud portal:
However, this didn't do anything for me and I get the same error.
So now I am left kinda stranded. Has anyone had this issue and know how i can connect to my remote machine from perforce?
From the comment below when i type p4 info i get the following:
User name: ******
Client name: PerforceServer
Client host: PerforceServer
Client unknown.
Current directory: c:Users*****
Peer address: 127.0.0.1:50413
Client address: 127.0.0.1
Server address: PerforceServer:1666
Server root: C:Users*****VersionControl
Server date: 2018/11/21 14:44:12 +0000 Coordinated Universal Time
Server uptime: 00:01:27
Server version: P4D/NTX64/2018.2/1724420 (2018/11/02)
Server license: none
Case Handling: insensitive
However using the prefix PerforceServer:1666 i still cannot connect
When running netstat:
TCP 127.0.0.1:50688 PerforceServer:1666 TIME_WAIT
TCP 127.0.0.1:50689 PerforceServer:1666 TIME_WAIT
Also if i run p4d i get the following error:
Perforce server error:
Listen 1666 failed.
TCP listen on 1666 failed.
bind: 0.0.0.0:1666: WSAEADDRINUSE
windows
azure perforce helix-server asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
This is a Perforce issue, not Azure... perforce.com/perforce/doc.051/manuals/p4guide/02_connect.html
– Rthomas529
Nov 21 '18 at 14:40
@Rthomas529 ive updated my question if you know a solution to my problem i would be very grateful
– Marc Rasmussen
Nov 21 '18 at 14:49
Is perforce service is actually running. When you install servers like this you usually need to start the service and configure it to start on server reboots. Also make sure the server can be pinged or telnet to it.
– Rthomas529
Nov 21 '18 at 14:57
@Rthomas529 since i can do p4 info and it tells me information about the server i am guessing it is started i can also see it in my services window
– Marc Rasmussen
Nov 21 '18 at 15:02
run a netstat -i on the server. What ports are listening?
– Rthomas529
Nov 21 '18 at 15:22
|
show 2 more comments
I am trying to set up my Azure Virtual machine to become a Perforce remote repository server.
First let me take you through the installation of Helix on the server:
And after the install is complete it says:
So far so good now from my client computer (my local desktop) I attempt to connect to this server, however, I get an error:
Now first I thought that the port wasn't open in my inbound so I added the following network rule in my Azure cloud portal:
However, this didn't do anything for me and I get the same error.
So now I am left kinda stranded. Has anyone had this issue and know how i can connect to my remote machine from perforce?
From the comment below when i type p4 info i get the following:
User name: ******
Client name: PerforceServer
Client host: PerforceServer
Client unknown.
Current directory: c:Users*****
Peer address: 127.0.0.1:50413
Client address: 127.0.0.1
Server address: PerforceServer:1666
Server root: C:Users*****VersionControl
Server date: 2018/11/21 14:44:12 +0000 Coordinated Universal Time
Server uptime: 00:01:27
Server version: P4D/NTX64/2018.2/1724420 (2018/11/02)
Server license: none
Case Handling: insensitive
However using the prefix PerforceServer:1666 i still cannot connect
When running netstat:
TCP 127.0.0.1:50688 PerforceServer:1666 TIME_WAIT
TCP 127.0.0.1:50689 PerforceServer:1666 TIME_WAIT
Also if i run p4d i get the following error:
Perforce server error:
Listen 1666 failed.
TCP listen on 1666 failed.
bind: 0.0.0.0:1666: WSAEADDRINUSE
windows
azure perforce helix-server asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
I am trying to set up my Azure Virtual machine to become a Perforce remote repository server.
First let me take you through the installation of Helix on the server:
And after the install is complete it says:
So far so good now from my client computer (my local desktop) I attempt to connect to this server, however, I get an error:
Now first I thought that the port wasn't open in my inbound so I added the following network rule in my Azure cloud portal:
However, this didn't do anything for me and I get the same error.
So now I am left kinda stranded. Has anyone had this issue and know how i can connect to my remote machine from perforce?
From the comment below when i type p4 info i get the following:
User name: ******
Client name: PerforceServer
Client host: PerforceServer
Client unknown.
Current directory: c:Users*****
Peer address: 127.0.0.1:50413
Client address: 127.0.0.1
Server address: PerforceServer:1666
Server root: C:Users*****VersionControl
Server date: 2018/11/21 14:44:12 +0000 Coordinated Universal Time
Server uptime: 00:01:27
Server version: P4D/NTX64/2018.2/1724420 (2018/11/02)
Server license: none
Case Handling: insensitive
However using the prefix PerforceServer:1666 i still cannot connect
When running netstat:
TCP 127.0.0.1:50688 PerforceServer:1666 TIME_WAIT
TCP 127.0.0.1:50689 PerforceServer:1666 TIME_WAIT
Also if i run p4d i get the following error:
Perforce server error:
Listen 1666 failed.
TCP listen on 1666 failed.
bind: 0.0.0.0:1666: WSAEADDRINUSE
windows
azure perforce helix-server windows
azure perforce helix-server asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
edited Nov 21 '18 at 21:52
Marc Rasmussen
asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
asked Nov 21 '18 at 14:21
Marc RasmussenMarc Rasmussen
6,16949129234
6,16949129234
This is a Perforce issue, not Azure... perforce.com/perforce/doc.051/manuals/p4guide/02_connect.html
– Rthomas529
Nov 21 '18 at 14:40
@Rthomas529 ive updated my question if you know a solution to my problem i would be very grateful
– Marc Rasmussen
Nov 21 '18 at 14:49
Is perforce service is actually running. When you install servers like this you usually need to start the service and configure it to start on server reboots. Also make sure the server can be pinged or telnet to it.
– Rthomas529
Nov 21 '18 at 14:57
@Rthomas529 since i can do p4 info and it tells me information about the server i am guessing it is started i can also see it in my services window
– Marc Rasmussen
Nov 21 '18 at 15:02
run a netstat -i on the server. What ports are listening?
– Rthomas529
Nov 21 '18 at 15:22
|
show 2 more comments
This is a Perforce issue, not Azure... perforce.com/perforce/doc.051/manuals/p4guide/02_connect.html
– Rthomas529
Nov 21 '18 at 14:40
@Rthomas529 ive updated my question if you know a solution to my problem i would be very grateful
– Marc Rasmussen
Nov 21 '18 at 14:49
Is perforce service is actually running. When you install servers like this you usually need to start the service and configure it to start on server reboots. Also make sure the server can be pinged or telnet to it.
– Rthomas529
Nov 21 '18 at 14:57
@Rthomas529 since i can do p4 info and it tells me information about the server i am guessing it is started i can also see it in my services window
– Marc Rasmussen
Nov 21 '18 at 15:02
run a netstat -i on the server. What ports are listening?
– Rthomas529
Nov 21 '18 at 15:22
This is a Perforce issue, not Azure... perforce.com/perforce/doc.051/manuals/p4guide/02_connect.html
– Rthomas529
Nov 21 '18 at 14:40
This is a Perforce issue, not Azure... perforce.com/perforce/doc.051/manuals/p4guide/02_connect.html
– Rthomas529
Nov 21 '18 at 14:40
@Rthomas529 ive updated my question if you know a solution to my problem i would be very grateful
– Marc Rasmussen
Nov 21 '18 at 14:49
@Rthomas529 ive updated my question if you know a solution to my problem i would be very grateful
– Marc Rasmussen
Nov 21 '18 at 14:49
Is perforce service is actually running. When you install servers like this you usually need to start the service and configure it to start on server reboots. Also make sure the server can be pinged or telnet to it.
– Rthomas529
Nov 21 '18 at 14:57
Is perforce service is actually running. When you install servers like this you usually need to start the service and configure it to start on server reboots. Also make sure the server can be pinged or telnet to it.
– Rthomas529
Nov 21 '18 at 14:57
@Rthomas529 since i can do p4 info and it tells me information about the server i am guessing it is started i can also see it in my services window
– Marc Rasmussen
Nov 21 '18 at 15:02
@Rthomas529 since i can do p4 info and it tells me information about the server i am guessing it is started i can also see it in my services window
– Marc Rasmussen
Nov 21 '18 at 15:02
run a netstat -i on the server. What ports are listening?
– Rthomas529
Nov 21 '18 at 15:22
run a netstat -i on the server. What ports are listening?
– Rthomas529
Nov 21 '18 at 15:22
|
show 2 more comments
1 Answer
1
active
oldest
votes
Allow the port through the Windows firewall.
1)Press Windows logo + X keys on the keyboard and select Control panel from the context menu.
2)Select System and Security from the options and click on Windows Firewall from right side panel of the window.
3)Click on Advanced settings and select Inbound Rules from left side panel of the window.
4)Click on New Rule under Actions tab from right side panel and select Port radio button from the window.
5)Follow the onscreen instructions and check if the changes are effective.
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2fstackoverflow.com%2fquestions%2f53414151%2fperforce-windows-server-2016-cant-connect-from-client%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Allow the port through the Windows firewall.
1)Press Windows logo + X keys on the keyboard and select Control panel from the context menu.
2)Select System and Security from the options and click on Windows Firewall from right side panel of the window.
3)Click on Advanced settings and select Inbound Rules from left side panel of the window.
4)Click on New Rule under Actions tab from right side panel and select Port radio button from the window.
5)Follow the onscreen instructions and check if the changes are effective.
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
add a comment |
Allow the port through the Windows firewall.
1)Press Windows logo + X keys on the keyboard and select Control panel from the context menu.
2)Select System and Security from the options and click on Windows Firewall from right side panel of the window.
3)Click on Advanced settings and select Inbound Rules from left side panel of the window.
4)Click on New Rule under Actions tab from right side panel and select Port radio button from the window.
5)Follow the onscreen instructions and check if the changes are effective.
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
add a comment |
Allow the port through the Windows firewall.
1)Press Windows logo + X keys on the keyboard and select Control panel from the context menu.
2)Select System and Security from the options and click on Windows Firewall from right side panel of the window.
3)Click on Advanced settings and select Inbound Rules from left side panel of the window.
4)Click on New Rule under Actions tab from right side panel and select Port radio button from the window.
5)Follow the onscreen instructions and check if the changes are effective.
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
Allow the port through the Windows firewall.
1)Press Windows logo + X keys on the keyboard and select Control panel from the context menu.
2)Select System and Security from the options and click on Windows Firewall from right side panel of the window.
3)Click on Advanced settings and select Inbound Rules from left side panel of the window.
4)Click on New Rule under Actions tab from right side panel and select Port radio button from the window.
5)Follow the onscreen instructions and check if the changes are effective.
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
answered Nov 21 '18 at 16:34
Rthomas529Rthomas529
183212
183212
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53414151%2fperforce-windows-server-2016-cant-connect-from-client%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
This is a Perforce issue, not Azure... perforce.com/perforce/doc.051/manuals/p4guide/02_connect.html
– Rthomas529
Nov 21 '18 at 14:40
@Rthomas529 ive updated my question if you know a solution to my problem i would be very grateful
– Marc Rasmussen
Nov 21 '18 at 14:49
Is perforce service is actually running. When you install servers like this you usually need to start the service and configure it to start on server reboots. Also make sure the server can be pinged or telnet to it.
– Rthomas529
Nov 21 '18 at 14:57
@Rthomas529 since i can do p4 info and it tells me information about the server i am guessing it is started i can also see it in my services window
– Marc Rasmussen
Nov 21 '18 at 15:02
run a netstat -i on the server. What ports are listening?
– Rthomas529
Nov 21 '18 at 15:22