Clever Geek Handbook

Perforce server: runs on public IP instead of 127.0.0.1

During installation (on Windows Server 2012), the installation asks for a port and then the server starts up on localhost (127.0.0.1). When I try to connect to the server using the computer's public IP, it won't connect. I tried using the P4PORT option to change localhost to Public IP. But then the Perforce service won't start (error 1067). Not sure why they bind the default port to localhost. Perforce works fine if a client on one server tries to connect using localhost: 1666, but obviously it's useless as clients on other computers can't connect. Any pointers?

[more] This server is an Azure VM. It has an internal IP address and a public IP address. On the same server, when I lauch P4Admin and type localhost:1666

, it works. It also works when I log in <computername>:1666

. It also works when I use <Internal IP>:1666

. It does NOT work when I log in <Public IP>:1666

. The machine is fully accessible over the Internet using a public IP address.

+3


source to share


1 answer


Decided. A new endpoint has been created on the Azure Portal with an open port 1666 and a private port 1666. I am assuming that it provides a mapping between external and internal IP addresses and ports. Thanks everyone.



+3


source






More articles:


All Articles