When I just start the pfSense, both Netflix and Prime works fine, I can login and watch contents, but after one day or so of my pfSense being online, I just can't login to those video streaming services anymore.
For Netflix I get the "NW-2-5" error and for Prime I receive a message saying there are connectivity issues. Then I have to reboot my pfSense and after that everything is working fine for, again, one day or so.
My guess is this has nothing to do with the firewall rules, as it works for one day or so, but just in case I took a screenshot of it, in the Block separator I isolated my other VLANs (Home, VPN BR and Guest):
I'm still learning about how to configure my pfSense correctly and I hope this is just a silly configuration mistake.
Any suggestion about what I should change or check in the configuration?
Related
I use CheckPoint VPN to log in to my place of work's servers to work remotely. The VPN has been working (mostly) fine all year, and I haven't changed any of the settings, but this morning, when I tried to log in, it's giving me the "Arg_NullReferenceException." I can't seem to find anything on this particular error on google.
I have tried restarting my computer, because it's not the first issue I've had with CheckPoint VPN (though it is the first time I've seen that error message), and a restart usually resolves whatever issue I'm having. I've also tried creating a new connection with the same settings, but I'm getting the same error with that one, too.
I'm not entirely sure what other information I would need to provide. I'm also not sure if it's a problem on my end, or on the company servers. I have already emailed tech support, but I thought I should be thorough.
This is a known issue. I have been jumping through hoops trying to get the capsule client to work. Raise a ticket with TAC if you have support. If not then you can download the E86 Endpoint connect client and run it. That has been my work around for this issue.
They just issued an update to the Capsule via the Microsoft Store. It seems one of the recent Windows Security Update broke the L2TP protocol within windows.
I am having an issue understanding the problem of why my site will load on some networks, but not others.
I am getting "ERR_NAME_NOT_RESOLVED" on Chrome in the following environments:
1) Office Network - This made me believe that it was a firewall issue
2) Open WiFi Network at a Coffee Shop - This made me believe that it was not a firewall issue
I am able to access the site without any issues from my home network and also when turning my phone into a hotspot.
I did some digging and was hopeful that adding an IPv6 record to my DNS would have resolved the issue(Maybe those networks were pulling from IPv6) but that also did not resolve the issue.
I ended up running a test on MXToolBox.com and received these warnings back.
MXToolBox Response
I do not have any email setup with this domain so I am not concerned about the email record errors, but the one I can't figure out is the top one with Category: DNS and the message of "DNS Record not found". The "More Info" link says "We did not find a DNS record at the location specified. You should check with DNS provider to ensure the record has been published and there are no typos."
I have an A record pointing to the correct IP(As I am able to access it from my home and cell phone networks). I added an AAAA record for IPv6(Though not sure I fully understand why it's necessary). My A record has been added for several weeks now, so it's not a propagation issue and my AAAA record was added a few days ago with a SOA of 10 minutes, so do not believe it to be a propagation issue either.
I have opened this question because I'm not even sure how to google this any further as everything returned back is typically client side(Clear your cache/cookies) and not what my issue is.
My VPS is hosted by Linode.
Thanks in advance for any advice/help.
Hey so I have three GCE instances set-up which all run the same code. They're cloned from the same snapshot so I'm pretty positive that they're exactly the same.
For some reason, only one of these GCE instances is able to receive connections from external sources. The other two can't. I keep getting a "Connection timedout" error in Firefox.
These instances all have the same network-tags, so they should have the same firewall rules. That is, if you're hitting this problem too, make sure you have the right firewall rules set in the networking tab of your google-cloud center before reading on.
Since they're running the same code and have the same ports open, I have no idea what the problem could be, or how to figure out what it might be.
I was wondering what the best way to debug this might be? I believe they were working earlier but now are no longer working.
Rebooting the instance seemed to fix this. This is not an adequate solution however. I'll update my answer over the coming weeks if it happens again.
I'm having a lot of trouble with an EC2 instance and I can't figure out what's going on. We're using it as a web server and it seems to work fine for single connection stuff - loading a simple page, RDP connection, ping etc. But as soon as a single client computer has more than one connection active with the server (a good example is if I try to browse the web site while I'm also logged into the server via RDP) the whole connection becomes incredibly unstable.
The biggest most annoying consequence of this is that the ASP.NET site that we're running consistently fails to load some pages since those pages use more than one connection. This wasn't a problem up until a few days ago when we were forced to migrate to different hardware because our hardware was apparently being retired by Amazon. Ever since then it's been tricky like this. Is it possible that there's a kink in Amazon's network and that it could potentially be resolved by stopping and starting the instance (and thus getting a different server?)
It turns out the problem was an underlying issue on Amazon's end. They investigated the issue and found a problem that they're correcting. I hope I haven't wasted too much StackOverflow brainpower with this dead-end of a question!
I have a website running a basic ASP.NET application that is mostly used from a single location, which is my client's office. The server is at a high-class datacenter.
Whenever I've been testing or using my application from outside their office I have consistently good connections but from their office the connection seems inconsistent. Sometimes requests just don't seem to make it to the server from the browser. I'm not familiar with the network hardware in the office, but they do have a T1 connection which should always be on.
I've tried ping and tracert and everything looks normal. When running Firebug during a failed request the request shows up in the log, then just sits there without showing it is sending any data, eventually it times out.
My question is, what tools can I use to diagnose this connection problem and start to narrow it down to a specific cause so I can fix it? Its an intermittent problem so a long running tool would probably make more sense, if there is any available.
Thanks for any help.
All of your standard ping and traceroute tools are probably your best bet. I'm not understanding though, where is the site located?
If you open command prompt, run ping -t aspwebsiteurl.domain <- will show if there is packet loss.
From command prompt again, tracert aspwebsiteurl.domain <- will show you what route the packet is taking to get the site. May also show you if there is one particular hop that is giving you the hickup.
Is there a proxy between the office and the datacenter that could be causing issues?
Also you could try Wireshark to try to debug the problem in more detail.
Speed Test - Internet Network Connection Speed may be of some help with some links to test out the connection at the client's office to see how well it works.
Another question is how far away is the client and the datacenter? If one is in New York and the other in Los Angeles then the distance apart may be a factor. Also, have you examined any possible DNS issues?