I'm getting the below "WSAECONNRESET" error when I try and connect with Perforce P4V on a VM I use.
"TCP receive failed.
read: socket: WSAECONNRESET"
This started late last week, it worked fine prior to that. I don't know of anything that has changed. The Perforce server is up and working because I can connect just fine from outside of the VM and other users aren't having any issues with it.
I can ping the server I'm trying to connect to from the VM just fine too. No firewalls are turned on. I have tried restarting the VM, my PC, and reinstalling Perforce (latest version). Any ideas?
Turns out that a few developers copied the same VM and we all had the same Mac Address. This didn't manifest in issues we noticed anywhere else, but Perforce couldn't handle it. Refreshing the Mac Address to eliminate this conflict resolved the previously mentioned Perforce errors.
Related
I am trying to install Oracle Client 19c when i starts the installation its freezes at stage 1, checked logs it hangs on "INFO: Checking whether the IP address of the localhost could be determined...", i refer some article to skip stage mentioned step but it also stuck on stage 7.
My System is in Domain
I tried the installation on recently formatted System and it worked with antivirus.
also tried to disable the Antivirus from my system but faced the same freezing issues. if unjoin the Domain and try it works.
I suspect the issue with any Domain Policy but dont understand the which policy is creating the problem, please suggest the solution.
If you are seeing "Reading from the pipe" message in ...\Inventory\logs OUT files then, login Windows with an admin account and run the services called "Server" and "Workstation".
I was trying to process GWAS data using plink1.9 with a rental AWS ubuntu server. I executed the plink commands from the terminal window in the Rstudio server.
It turned out that if I execute a plink command that overloads the server, my Rstudio server will become inaccessible and this problem does not revolve.
for example my Rstudio-server from port 8787 has become unavailable.
http://ec2-54-64-41-xxx.ap-northeast-1.compute.amazonaws.com:8787/
I accidentally did it twice. First time I did something like cat xxx.vcf (how stupid of me) and the server simply went frozen and the Rstudio server crashed.
Since I could still access the server with putty and winscp and so on I managed to get my files to a new instance. Then I tried to use plink to do some QC, something like
./plink --bfile xxx--mind 1 --geno 0.01 --maf 0.05 --make-bed --out yyy
It had again overloaded the server and the same Rstudio server trouble occurred again.
Now both instances are still accessible from putty, I logged on to check the running processes and it seemed to be fine. There were no active heavy jobs and no zombie processes either.
The CPU monitoring looks fine too.
With the only problem that the Rstudio-server link is not working.
Does anyone have similar experiences? Your advice is very much appreciated.
mindy
I'm running an elasticsearch server on my Mac and would like to connect to it from Windows 10 running in VM Ware fusion. I have my adapter running in Bridged mode. Everything I read seems to say I should just be able to use the Mac IP address to connect, but it's not working. I have firewalls turned completely off on both the Mac and Windows. I'm trying to access Kibana from Windows, so doing http://192.168.x.x:5061 from Windows browser, keep getting ERR_CONNECTION_REFUSED in Chrome. I'm able to ping the IP from the guest, so clearly it can see the host, but something is blocking the connection. I tried forwarding port 5601 on my router, that didn't work either. I do also notice that trying to use http://192.168.x.x:5061 on the Mac itself doesn't work either, which I think may be the source of the problem, but I have no idea how to fix that.
The issue isn't on the VM but your elasticsearch config ... if you cannot connect to it either with the Mac or the VM, it means that it is elasticSearch that's the issue.
Figured it out. I changed Kibana config file to bind to 0.0.0.0 instead of localhost. I thought binding to localhost or 127.0.0.1 automatically made it also include the LAN IP, but you learn something new every day...
I have successfully built the client and server modules from the Getting Started with Winsock tutorial.
I have a desktop and a laptop both connected to my wireless router – both running Windows 10.
Running the client module on the laptop, I am able to successfully transmit data back-and-forth to the desktop (running the server module) using the desktop's IP address.
Running the client module on the desktop with the laptop's IP address as the command line argument, I get an "Unable to connect to server!" message after a ten second delay.
If I try to run both modules on the desktop in separate console windows using the "localhost" command line argument, the client console displays "Bytes sent: 14" and hangs waiting for a response from the server – however this works if I use either the desktop name or the desktop IP address in place of "localhost".
I am able to run both modules on the laptop using either "localhost", the laptop name, or the laptop IP address as arguments.
I have gone through the same motions with port 27015 forwarded on the router and incoming and outgoing firewall exceptions added to both the desktop and the laptop – there is no difference either way.
Any assistance would be greatly appreciated as I cannot figure out why this works in one direction but not the other.
Thank you for the suggestions Karsten and Andriy. I first tried getting the two computers to ping each other and neither was successful. After researching online, I was able to get them to ping after turning on "echo requests" in the firewall settings, but my original problem persisted. I then tried turning off both firewalls and I was able to get my server and client programs to work both ways. That wasn't a great long-term solution, so I tried selectively disabling the firewalls and realized it was an issue on the laptop's end. I noticed that my "server.exe" program was in the allowed apps list twice – one instance granting private access and one granting public access – but only one instance was active. I deleted both and added "server.exe" again with both public and private access boxes checked, which solved my issue.
I know this is similar to a lot of questions on here, but I feel it's worth a new question since I have yet to discover a question that fully encompasses my problem. I've been struggling with this for a couple weeks, read pretty much every answer to every question about it on here, as well as countless blogs, articles and other Q&A forums. So, here goes:
I created a service to monitor several things on our network and update a database with the information. Moved it to a server and went threw a lot of frustration with getting the WMI and DCOM settings right so that it would work.
I recently had my computer crash on me and so I lost my code and had to recreate the service from scratch/memory. It runs perfectly fine on my laptop. I moved it to a server(different than the one that is running the old version of the service). It runs there, but it is unable to reach the PCs I am monitoring. I try running the command line WMI query and can't connect there either. Getting the 'RPC Server is unavailable' error.
I've tried changing settings as per all of the articles/answers I've been able to find and cannot get it to connect.
A few relevant things:
All the RPC/WMI related services are running on both server and
monitored PCs.
The firewall is disabled on both server and monitored PCs.
I know the user and password are correct and have admin rights
on monitored PCs.
Server in question is (I believe, will confirm with someone later)
Windows Server 2008 R2 on a virtual server, if that makes a
difference.
Able to ping PCs and run tracert from server.
Here's where it doesn't make sense to me. I am able to run the wmic command from my laptop to the monitored PC. And from my laptop to the server. Wmic works locally on the server, but whenever I try to make a remote call, it fails with the RPC error.
I don't know much about networking, and we are a small company so we don't really have a Network Admin or anything. So, any and all advice would be appreciated.