- 최신
- 최다 투표
- 가장 많은 댓글
Hello! Some questions that will aid you:
- Are you able to resolve aws.mycompany.com to an IP address? You can use the dig or ping command to find out.
- How did you mount the network filesystem? Which syntax did you use? Have you tried unmounting and mounting again?
- Have you checked the security groups and network acls applying to the instance?
- Do you have any firewall on the Linux OS that might be blocking connectivity?
- Does the source share apply any network filtering on their side to only allow specific hosts?
Thank for the reply Franscisco. Here is my answers:
- Yes, it´s possible to ping. I even tried to connect with the ip number, \\99.99.99.99\folder$;
- I'm sorry, I don't know what you mean, but the shared folders configuraration were create on samba, smb.inf;
- Yes, all the security was checked;
- There is no firewall on the Linux, and I tried do disable the firewall on the client side as well;
- There is no filtering.
Only some Windows clients can't acess the folder. The majority of users on windows clients acess the folder withou any problem.
One more detail that I realise now. When I'm using my regular network I can acess the folder. Now, I'm trying to use the shared internet connection from my cell phone, and I can't connect to the folder anymore.
Hello! Since you are able to access it from your regular network, this means that there's no issue on the share side and you should investigate the shared cellphone connection instead. I would suggest to contact your cellphone provider, they are likely to block TCP port 445 for security reasons which is needed by SMB. There's no way around this other than to use another network.
