I have just installed a Redis Cache on a windows server using the rdis package (https://github.com/MicrosoftArchive/redis).
It runs under localhost fine.
My problem is what do I need to do to connect to this cache instance from a remote connection?
I am trying to connect to the ip address of the server I get the below error. I get the same error using the server name.
What needs to be done to expose the cache?
modify the redis conf, set the protected mode to no and bind the public ip of your machine.
Related
I have set up the fabric-ca-server in a vm. Now it is needed to access the server remotely. So I am looking for the possibilities for such access.
I have tried something like changing the hosts in csr.json file. In that, I specified the ip address of vm. But I need to know actually how to access the server remotely.
You can expose the fabric-ca-server port with host in your docker compose, then it can be accessed using exposed port.
My setup is an infinispan 8.1.2 server running on AWS using a distributed cache. For local development, I would like to be able to connect to the instance on AWS, but the server will only start using either 0.0.0.0 or the AWS private IP address. Since JGroups does not work with the 0.0.0.0 address it seems my only option would be to use the AWS private IP. But this address is not accessible remotely!
Has anyone else run infinispan server and tried to connect from a different subnet?
Not sure if this helps but anyway...
You do have a public IP address on AWS, which you can query with some HTTP command (check the docs).
Now, if you can add a NATting rule which forwards traffic between the private and public address, you could use external_addr and external_port in TCP to bind to the private address, but send traffic to the public address.
This would allow you to access a JGroups node from another subnet, or even the internet. You probably have to modify your security policy and expose the externally accessible ports. YMMV
I am using Windows server 2008 and installed wamp on it. Now I want to share the local link with client using same network.
Instead of [localhost], I am trying [server_ip_address]. but it's giving me error.
I want to use it as 192.168.30.1 but not able access this.
I also put the wamp online and restart the server. I m able use the ip from my m/c only. If I use this link from another m/c then its giving following error
URL http://192.168.5.12:8080
Error The connection has timed out
you can access the Server from your clients with url like,
http://server ip address : port
Your Local clients and your Local server must be connected in a LAN network.
Check your Windows firewall settings. Check by turning off the private network firewall
I had a perfectly running remote redis-server on my LAN (# x.x.x.x:p). I was able to use the RedisDesktopManager to view the server contents. However, there were a lot of dangling connections to my server from different clients (subscribed to channels) which I wanted to close so I used the SHUTDOWN command from the console of the desktop manager. Since them, I am unable to connect to the remote server. The desktop manager is running and lets me add a new redis-server connection but I am not able to connect to the previous server connection. Whenever I try to connect to the server # x.x.x.x:p, the desktop manager terminates. I have not made any configuration changes to the previously running server so I am sure that I am not making any mistake with port bindings. Any help on what I am missing will be really appreciated.
Thanks in advance!
The problem was with the configuration binding. The bind line in the configuration file was originally
bind 132.168.131.129 127.0.0.1 0.0.0.0. I changed it to bind x.x.131.129. The server connection was restored.
When I try to create a Distributor on a SQL Server 2012 database I get the following error. I have tried a lot of things over the last 6 hours and can't get anything to work. Does anyone have any ideas?
This is a general connection error.
Are you configuring a remote distributor? Is the remote distributor named "LPUAT\"?
Here is a list of things to try:
Verify you are connecting to the right server.
Try pinging the server by machine name.
Try pinging the server by ip address.
Verify the target instance SQL service is started.
If the target instance is a named instance then make sure you are specifying a named instance when configuring distribution.
Verify the target instance has TCP enabled.
Verify the browser service is running on the target service if it is a named instance.
Temporarily disable any firewalls, then try to configure distribution, to see if your being blocked by a firewall.