Hi everyone,
We are currently in the process of migrating our OutSystems OnPremise infrastructure to a Cloud infrastructure (O11).
One of our applications writes files to a local fileserver using the FileSystems Forge Component. However, after migrating the code to the cloud, we are encountering an error stating that the network path was not found.
We have already set up a VPN between the cloud and our company network. Despite this, the code is still not functioning as expected.
Our Situation:
Our Question: Are there possibilities to still use the same code within the cloud environment? If so, what steps do we need to take to ensure the network path is accessible?
Any guidance or suggestions would be greatly appreciated!
Thank you in advance for your help.
Hello,
We are using this component over the VPN and this works fine.What are you using for the Path. We use something like:\\192.168.178.95\ApplicationdataI presume on the onpremise you used the Netbios name. Don't think you can use it on the Cloud.
If you are using something like\\share.mycompany.local\Applicationdata you can add the Dns for mycompany.local and resolve the name by you're DNS server. (adding local DNS can be done by creating a ticket)Kind regards,Robert de Vries
Hi Robert,Thank you for the feedback, it is much appreciated.We were indeed using the Netbios name.I have now tried using the IP as you proposed but i encounter the same errorI tried to ping the IP from the cloud. Despite having verified that the IP adres is defined within the VPN Settings in lifetime, i'm getting a time out.
I'll contact our system engineer to see if he can identify any issues on his end and update the post accordingly.
Ping on the Cloud doesn't work while ICMP is switched off at OutSystems. I guess you are using the NetworkTools. Try to connect with the Telnet cmd.I checked to the ip with port 445 and that give's a port open.Otherwise indeed a firewall is in between or routing is not in place.
Robert,
Thank you for the additional information.
I have checked with our system engineer, and he does not see any traffic over the VPN tunnel when I try to connect to the IP using the FileSystem Server actions. (SMB Traffic?)
As a test, I sent an HTTP request to the server from within the cloud and this was working, so we are able to connect to the local server.
Do you have any other ideas on what we might be missing?
Thanks againThibaut
If there's no traffic over the VPN tunnel, then there's something preventing that traffic. Are you using IP-addresses now, or still something that needs DNS resolving?
I'm using the IP implementation from Robert first reply.example: \\192.168.178.95\Applicationdata
Could be a protocol/port restriction? Normally for security reason, not all protocols/ports are open.
Hi Pedro,Thanks for the reply.Wouldn't the system engineer still detect traffic if this was the case?
Not if it's blocked at the cloud side. The system engineer can only see what arrives on-premise.
Hi Killian,Thanks for the reply.Does that mean i have to check with our internal System engineer who set up the VPN , or does Outsystems control that side ?
Kind RegardsThibaut
Ho Thibaut,
As I know it can be configured in both VPN points or/and between using a firewall.
So if the configuration is in origin VPN or firewall between destination VPN I think that don't originate traffic.
We were unable to resolve the issue with the FileSystem component, even with the assistance of OutSystems Support.However, we found an alternative Forge component that appears to be specifically designed to address this Cloud/fileSystem issue.
Great you found a solution, and thanks for letting us know.