I'm trying to mount a windows folder (machine1) under linux (machine2).
Computers are in the same private network.
To achieve this I use:
mount -t cifs -o user=... PATH_ON_MACHINE1 PATH_ON_MACHINE2
I've spent some time on getting only timeouts and it suddenly occurred to me that maybe a firewall is blocking the connection. I turned off the firewall and was able to connect to my shared folder. Unfortunately I cannot leave it like this.
I went to the "Windows Firewall with Advanced Security" window and enabled everything from the group "File and Printer Sharing" however I'm still getting timeouts.
So my question is:
What other services should I enable in order to be able to connect to the shared folder from linux?
Just for other people with the same problem.
The service is called: Netlogon Service/Inbound Rules.
Related
I accidently broke my centos VM in azure by twiddling firewall rules within it. After a reboot, the normal ssh access is not working anymore. Is there any chance to get into that VM, any console login directly to the machine somehow?
After reading the current state (April 2016) at microsoft about this, I've decided to dump the virtual machine and set it up again:
This one-directional access is just a start. Console screenshots and serial output can help identify a problem, but they are not the solution for resolving the problems. We are working on enhancements that will enable secure bi-directional access to the console of the virtual machine. This will enable additionally debugging capabilities, and, more importantly, the ability to resolve a set of common problems through the bi-directional access. Right now, I don’t have a timeline but we know this is critical.
(article)
This is odd to me:
I have jupyter notebook installed on a vm machine, it is working fine from localhost:8888/tree. The vm machine has an address of 192.168.112.150, I assume the site can be accessed from my desktop browser by typing: 192.168.112.150:8888/tree
I receive error saying:
This site can’t be reached
192.168.112.150 took too long to respond.
I checked firewall settings on my desktop, it's opened; on the vm machine, I made some adjustment, here is the settings:
I have no problem ping the vm machine from my desktop
Can anyone enlighten me how to fix the issue? Thank you very much.
Updated: I receive this error message when I ran it with --ip=0.0.0.0
By default, the Jupyter Notebook only listens to incoming connections on localhost--it has zero permission checking or built-in safeguards otherwise. Adding --ip=* to the end of the command will have it listen on all of your network interfaces.
I am maintaining a Virtual Machine on a Cloud Service with Linux (SLES) operating system. At some point, someone logged in, did some major things (e.g. chmod 777 on ALL files, etc) and, with some other things that he did, messed up the system.
It would be no surprise if he actually hacked it, but...
The vm is hosted inside a VPN (unreachable from outside the VPN), and last root command specifies a user connected through tty1 (!!!), with no IP address, while all my connections, root and user are pts/X.
My thoughts (not like I am an expert) are concluding on one thing, this user must have physical (?) access to cloud service, since tty is reachable locally.
Which means, that if that is true, the "attacker" must be someone from inside the Cloud-Service hosting company.
Question:
Is there ANY way you can connect remotely to a server/cloud service virtual machine using ttyX?
Correct me at any point you see wrong; as I mentioned I am not an expert but I am more than willing to learn.
Depending on the hypevisor, it provides a remote console, so, it is kind of local console connected from a remote place. Also, there is a ipmi protocol that can connected to the hypervisor and use the sol (serial-over-lan) command.
Other than that, the user might be connecting using a VNC, that would also be shown as a tty connection
IPMI SOL: http://www.alleft.com/sysadmin/ipmi-sol-inexpensive-remote-console/
Remote qemu guest console: How to switch to qemu monitor console when running with "-curses"
VNC on guests: https://askubuntu.com/questions/262700/qemu-kvm-vnc-support
I connected two laptops using a cross-over cable. My IP Address is 192.168.1.1 and the other IP Address is 192.168.1.16. We both are able to ping each other and the reply is perfect. There is no loss of packets.
The problem is I shared a file and the other system is not able to open my IP Address using the run command. Even I am not able to open my Shared folder by giving in the run (\\192.168.1.1). A dialogue box with the message \\192.168.1.1, The Network Path was not found opens each time we try this.
But I am able to open his shared folder by giving in run command (\\192.168.1.16). I closed all the firewall services in my system. But still my system is not able to respond. Also we are not able to use remote desktop connection.
Can anyone please help me in solving this?
Additional Details: I use Windows XP and the other machine uses Windows 7. We both are in the same work group.
Here are some steps to solve your problem:
Did you set the static IP by yourself or that come automatically?
If yes then please go and set the IP manually
Then share the file and put the permission of that file to Maximum (If you believe your partner)
Then power down the firewall or antivirus for some moments (say 10 minutes)
Now try to connect using the \192.xxx.xxx.xxx method using the Run window
If the 5th step is not working, then try disabling and reenabling the LAN card, then try the 5th step again.
Hope that solved your problem.
Remote Desktop needs to be explicitly enabled. Right click on "My computer", go to properties and look at the remote settings tab.
I advice you to use Radio Access Point to connect both windows 7 and windowsXP. I think this is best choice of troubleshoting jaringan. why?
Because I already do anything to connect both Operating System but can't solve that problem.
I am trying to setup NFS mounts between two machines on the same local network, however it seems I need to be more specific in my firewall (FIREHOL) setup as the client side cannot mount the exports.
Did look at netstat to determine the ports that open up, but they seems to be non-static/changing.
I know it is firewall related as disabled/stopping my Firehol causes the problem to dissapear.
Any specific areas I should investigate?
Well, first of all, you need to make sure that portmap is also enabled in your Firehol configuration.
I am not super sure about the low level workings of NFS's ports, but it does not use the same ports everytime.
You could do something like the following to enable the NFS ports, as well as portmap. (Check rpcinfo -p)
This would enable the rpc queries (to determine the ports, for the firewall, to know AFTER NFS was started(or restarted))
I also suggest the use of 'src' to restrict the client IP's you are serving to, if you don't already have it :)
Lastly, remember to restart the firewall/firehol AFTER nfs restarts, so rpcqueries are happy with the ports for nfs service.
Example (where 192.168.152.176 is your client machine)
server portmap accept src 192.168.152.176
server nfs accept src 192.168.152.176