rich_tech Posted June 5, 2017 Posted June 5, 2017 (edited) Hello All, I have a bit of a weird one, I have two azure environments - 1 classic and 1 RM based one on the new portal which I am looking to use and retire the old portal. I have set them both up as site to site VPNs connecting in to our base site here, they both have identical connections to the azure environment which work the same, its the same firewall for them both, that bit appears to be working spot on, data is travelling both ways. When I create a server in the Azure RM portal, I can SMB browse servers across from Azure to the LAN site at our base fine which is what I want, but I cannot browse the server from the LAN at our office, it wont actually browse it, wheras our Azure classic portal environment, I can network browse the boxes as though they are on the LAN normally. I have followed a lot of guides about this and looked at the NSG settings trying things out, but still the classic portal based servers work fine and can be browsed and pinged internally fine, just not the RM based stuff, but I wanted to know if anyone else has had these issues so far and how they overcame them ? Or has a definitive document on how to achieve this ? I do not want to look at Azure File Storage as I don't want to over-complicate things for our users within the group I work for. Edited June 6, 2017 by rich_tech
rich_tech Posted June 6, 2017 Author Posted June 6, 2017 Sorted this issue, basically Sonicwall despite saying it would autocreate the access rules, did not actually create anything, once I did it manually it fired into action.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now