Message 1 of 3
F360 and corporate proxy
Not applicable
04-12-2016
11:31 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I've been trying out Fusion 360 and I think it's great and would be a really nice switch for my engineering group. The only problem is a big one though. Something about our corporate proxy or something network related doesn't play well with it so I literally have to use it in offline mode at work which is a deal killer in terms of adopting it for the team. I know the current answer is "have IT open x y & z ports & non-authenticating proxy, etc, etc...".. The problem is we're just one part of a large global corporation. They don't make exceptions like this just so one small group can connect to a certain domain or two.
Given that there are millions of sophisticated cloud systems that seemingly work fine without needing these kinds of particular requirements, is it ever going to change for Fusion 360 or do I need to get over it and accept that it just won't be a solution for us? Considering so many companies have IT policies that are similar this seems like something that Autodesk would have an interest in working on.
Also is there any sort of diagnostic test or procedure to determining what specifically Fusion 360 isn't liking? I don't know which servers it's trying to reach that it can't, which ports, what type of proxy we have, etc. Is there some way I can narrow it down to " oh, it's because xyz.com can't be reached" or "everything is good except port 123" or "it's not working because we have an authenticating proxy"? A small program that literally just tested everything Fusion360 needs network-wise and spit out a report showing what's not working would be real help (certainly more useful than the ambiguous authentication error message, no login screen, or crashing at startup, all of which I've experienced at one time or another when launching the program in online mode while at work).
Given that there are millions of sophisticated cloud systems that seemingly work fine without needing these kinds of particular requirements, is it ever going to change for Fusion 360 or do I need to get over it and accept that it just won't be a solution for us? Considering so many companies have IT policies that are similar this seems like something that Autodesk would have an interest in working on.
Also is there any sort of diagnostic test or procedure to determining what specifically Fusion 360 isn't liking? I don't know which servers it's trying to reach that it can't, which ports, what type of proxy we have, etc. Is there some way I can narrow it down to " oh, it's because xyz.com can't be reached" or "everything is good except port 123" or "it's not working because we have an authenticating proxy"? A small program that literally just tested everything Fusion360 needs network-wise and spit out a report showing what's not working would be real help (certainly more useful than the ambiguous authentication error message, no login screen, or crashing at startup, all of which I've experienced at one time or another when launching the program in online mode while at work).