I'm learning network communication. Today I need to access files on a remote server in our local network, but in the first place I just typed the IP address. Instead of being asked for username and password, I could only get 403 error. My tutor pointed out that I omitted the preceding double backslash, and after I added it, things worked fine.
He didn't have time to explain all the details and left it to me. After some searching, I believe it has something to do with the URI specification, but I couldn't find what exactly the specification is and why the explorer would solve the input so differently.
Platform: both are Win 7 Enterprise Edition. I was working on IE 8.
Related
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?
I was setting up a database on mongodb for a project. Navigated to my own public IP address from firefox and got scared by this certificate error.
I asked the support at https://whatismyipaddress.com/ and they said it's unexpected behaviour.
I don't have control over this network as I am a renter.
Probably a trivial misunderstanding for someone who understands networks but I want to understand why this happens if there's potentially sensitive information in certificates.
Thanks
windows 10
firefox 98.0.1 (64-bit)
extensions: malwarebytes, duckduckgo, vim ixen, expressvpn, httpseverywhere
I am looking for a way to programmatically get the name of the vendor that owns a MAC address within a block/range that they purchased. Preferably by querying some API or database, language agnostic. Or if there is some other way that applications do it that I am unaware of.
For example, running nmap -sn 192.168.1.0/24 with root privileges yields
...
Nmap scan report for 192.168.1.111
Host is up (0.35s latency).
MAC Address: B8:27:EB:96:E0:0E (Raspberry Pi Foundation)
...
... and that tells me that the Raspberry Pi Foundation "owns" that MAC Address, within the prefix range that they own: B8:27:EB.
However, I am not sure how nmap knows this, nor how I could find this out myself. Parsing nmap output is not an ideal solution for me. Here's what I found from digging online:
This stackoverflow question references a site that appears to do this, however it appears to not have been updated since 2013, nor does it expose any API endpoints. Most notably, it does not have the newer block of MAC Addresses that the Raspberry Pi Foundation reserved for their newer models (under Raspberry Pi Team, or something along those lines).
I found that the IEEE handles these registrations through their site, however it appears to be for their customers and I could not find an exposed endpoint for their search function.
On that same IEEE page linked above, it looks like I can get a CSV file of their entire database. However that seems large, and would have to be actively kept up-to-date. Does nmap come with an updated database generated from those files locally?
If a public-facing API like I'm envisioning doesn't exist, I'll make one myself for fun. I'd first like to know if I'm thinking about this wrong and if there is an official, "canonical" way that I have not found. Any help would be appreciated, and thank you.
The maintainers of nmap keep a list of prefixes as part of the tool. You can see it here:
https://github.com/nmap/nmap/blob/master/nmap-mac-prefixes
They keep this up to date by periodically importing the public registry on this site:
https://regauth.standards.ieee.org/standards-ra-web/pub/view.html#registries
Note that those files are rate-limited so you should not be querying those csv files ad hoc as part of a software package; rather you should do what nmap does and keep an internal list that you synchronize periodically.
I'm not aware of a publicly available tool to query them as an API; however, creating one that works the same way that nmap does would be fairly trivial. nmap does not update that file more than once or twice a year which makes me suspect that the list doesn't significantly change often enough that keeping your own list would be too onerous (you could even download nmap's list every so often).
I apologize in advance for how vague this question is. I had a connection string to SQL Server 2012 on a remote server from my work laptop using Visual Studio 2015 and it worked well for connecting to my database to populate asp:dropdownlists etc. on my web app as well as generating reports using SSRS.
That was last week, today I'm getting the error indicated in the title of this post. Below is my connection string minus the specific server name and ip address. Something changed between last Friday and today that this error is popping up.
Provider=SQLOLEDB.1;Data Source=[Server Name];Initial Catalog=[Database Name];Network Address=[Server IP Address]
I admittedly am at a loss as to how to troubleshoot this. I would endlessly appreciate a few leads as to what I can check out, whether there is some sort of log that tracks failed log ins, or some other means of finding out the source of the problem, or what changed.
Thank you so much in advance for helping a brand new programmer.
The problem could be any of the above problems, or a SQL Server configuration issue, or a network problem, or a permissions issue. The first thing I usually try is connecting with SQL Server Management Studio with the same settings. This will give a much more detailed message with specifics of what is failing. In short, all of the numbers in the error message are important and help pinpoint the real problem. You can also use https://msdn.microsoft.com/en-us/library/mt750266.aspx for some other techniques to diagnose/repair the issue.
So, I recently installed synergy because I was tired of using two mice and keyboards. Problem is, set up is not working. First, the setup.
Server:
Desktop
Windows 7 64 - on our home network, part of Workgroup: WORKGROUP
Client:
work issued laptop
Windows XP SP2 32 - on home network, part of workd Domain: DOMAIN
Server is set up, all the computer names are correct. I'm a bit of a noob at networking things, and I don't want to mess up the configuration of my work laptop again (I already switched the domain to my workgroup, BAD). So, any suggestions that aren't too crazy please, since it's a company laptop.
I've tried putting in the ip on the client as well, firewall is allowing on the port in use, just can't get it to work. I think I'm SOL with the Workgroup/Domain difference though...
From what I remember, Synergy doesn't care about the workgroup and/or domain, it just needs to be able to communicate with the server/client IPs. Did you try to manually insert IPs of client/server?
In a very similar situation I discovered that when trying to ping my non-domain desktop with its workgroup name the dns resolver was appending the work domain to the desktops name. So when I tried synergy with an IP address I successfully connected the two computers.
The only caveat I can offer is maybe you needed to add the application to the windows firewall exception list for both machines. I would assume the port setting was the same between the two computers (default is 24800) in which case you should only use the IP address because the application knows to access 24800 via that setting in the advanced configuration.
You can add the program to the whitelist or specifically the port if you prefer via the Windows Firewall. On a side note - I am also using an older version of synergy (1.3.1) and not the latest as of this answer (1.4.2 Beta) which did not work for me, but I will assume it's because my server was running 1.3.1.
I chose not to update all 6 machines and their respective horrific configuration constructs that synergy loves to enforce upon us. [caution... rant: x is left of y and y is right of x... really? are you sure about that Einstein? Synergy could at least INFER that bit of logic instead of REQUIRING it!]
Hope that helps.