I just start with MongoDB.
I have installed it on Win Server 2008 R2 and hosted it in a win Service, worked.
I tried to connect from a Client using an app, but can't connect.
I checked the Connection string twice, correct (isn't that hard) and I stopped the Firewalls on both machines, nothing helped. The machines were part of a private Network, no Routers in between.
I also used mongo Shell (mongo.exe) on the Server, and I was able to connect.
So, it must be some issue with the Client machine or the Network.
Related
I have a flask app running on a remote WINDOWS server (this server has a fixed ip address) which is not on my local network. The flask app is used to return some json data. The app works fine when I try to access the data while being logged into the remote server through request module in Python. However, when I try to run the same script on my personal laptop (which is not on the same network as the remote windows server), I get an error. However, when I try to ping the remote server from windows command prompt, I get the answer back. Can somebody tell in which direction should I go? I have no experience with web / api development.
response = requests.get("http://127.0.0.1:5000/product/1)
But instead of the local ip address, if I substitute the remote ip address, I don't get anything back.
Ok, so the problem lied with the remote firewall, it was blocking incoming connections. The moment I switched off the firewall, everything started working.
I have a physical Window Server 2008 R2 machine running SQLBase 8.5 and I have no problem connecting to it. Recently I migrated this server to a virtual machine and the problem come up. Sometimes I am able to connect to the Server and sometimes not.
I can pin my Virtual Server but not able to connect to it through SQLTalk or any client application.
Is anyone having the same issue running SQLBase 8.5 on a Virtual Machine?
Thanks!
Check how many users connect at a time. SQLBase 8.5 have some limitation when maximum number of users/cilents exceedes.
Try to find whether the issue occurs when a large query is executed. If so then try to simplify it.
Check for blocking issues. Try to test its working when disabling Internet security applications\antivirus\Firewall for some time.
Check for port issues. Check the 'listenport' value of sql.ini file.
Check for SQLBaseConnection properties and cross check the parmeters like 'connection lifetime'.
SQLBase 8.5 was only ever certified up to Windows Server 2003, and is so old I'm amazed it runs at all. You should be running at least SQLBase v12 if you're on Window Server 2008.
Here is a compatibility matrix: SQLBase compatibility v6 to v12.2
So assuming your SQLBase instance is actually up and running at the time you can't connect, check the CLIENT side sql.ini , there will be an ip address e.g. .
On the CLIENT at command prompt, run: ping -t (ipaddressofserver in CLIENT sql.ini)
I am having trouble connecting to my virtual network using the azure VPN client on windows 10 (I get an error about the certificate not found).I found a way to manually configure the VPN, I can successfully connect to it, ping my virtual machines from my local machine, ping my local machine from my virtual machines, remote desktop to it with the virtual network IP address (or hostname) and even connect to my shared folders on my local machine from the Virtual machines. What I can't do, and want to do is to connect to my shared drives on the VMs from my local machine (it works perfectly when I connect with the azure vpn client from windows 7). I've noticed when you connect through the vpn client it actually sets up the routing tables for you. So my question is: How do you configure it manually with powershell?
PS: For some reason you can't go to the IPV4/6 or any properties on your VPN connection on windows 10, So i have to do everything through powershell.
The problem wasn't the routing tables. The problem was that there was credentials stored in my my Credential Manager (Control Panel\All Control Panel Items\Credential Manager) for the VM which was incorrect, I think, I cleared it, and all worked. And by the way, I got the Azure VPN client to work on my windows 10 machine with help from this article
I have some issues with MongoDB (or Linux security, perhaps):
1 I am runing MongoDB 3.0 in an OpenSuSE 13.1 machine (which acts as the data server). I have a local network of 4 computers with different OSs.
2 I can connect from a Windows 8.1 Laptop using the mongo command, using the pymongo Python library, or Robomongo. Everything works just fine: I can query the server and insert things.
3 However, when I try to access port 27017 to see the "It looks like you're accessing..." message, the browser says "The connection was reset".
4 SuSe's Firewall and AppArmor are disabled.
QUESTION: There is one computer that can't access the address of the local server. Said computer is in the same local network and is running Windows 8.1. I tried with many other devices and OSs (see miniupdate in comments) and they all managed to access the 27017 port on the server. Of course, the server simply displayed the message "It looks like you are trying to access MongoDB over HTTP on the native driver port.". Do you have any ideas as to why the browser in the problematic computer keeps saying "Connection was reset" instead of showing the message mentioned above? Please note that this computer can do everything I mentioned in point 2. It's the browser thing that is puzzling me.
MongoDB's default port doesn't speak the http protocol. Which is what a browser can speak (among a few others). If you're looking for the web based status page, then that should be on port 28017 (27017 + 1000).
See http://docs.mongodb.org/manual/reference/default-mongodb-port/ for more details.
Found the solution on my own: disable the "Web shield" of Avast Antivirus. It somehow resets the browser's connection to Mongo.
Again, I realize that Mongo doesn't talk HTTP on that port, but still the fact that all other devices but this one were able to connect (to simply get a message) was bugging me.
I have installed a SQL Express 2008 Server on my Desktop for some local work. This has mixed authentication. I have enabled TCP/IP connection so that one colleague can connect to this server. However, this exposes the server to everyone in the network. How do i keep track of which PC in the network connected to this server and when ? This would just help me audit the usage of the server.
Well you can get information about current users, sessions, and processes in an instance by using
sp_who;
MSDN Documentation