I fully expect the issues to be buried in my network, but as I inherited a completely undocumented network not more than a few months ago, finding the issue has proven difficult and the typical troubleshooting and fact finding steps have shown me little. Which brings me to this community from another network (phone hotspot) to ask for some help in identifying the issue.<\/p>\n
So here we go!<\/p>\n
I punch in community.spiceworks.com<\/a> into a brower and I get connection timed out errors in IE/Chrome/Edge<\/p>\n I do an nslookup and community.spiceworks.com<\/a> resolves to:<\/p>\n Name: 6396l.x.incapdns.net<\/a> I ping community.spiceworks.com<\/a>, 6396l.x.incapdns.net<\/a>, and 45.60.101.212 - all successfully<\/p>\n I run tracert, and route to our core switch, ASA, and then out to the ISP, various hops across the internet and eventually make it to the destination<\/p>\n We have an iBoss web filter, I put it in bypass and got the same results. To ensure it wasnt the iBoss, I grabbed a patch cable and took the iBoss out of the loop - no change<\/p>\n I checked firewall rules on several PCs and even outright disabled the firewall and antivirus software for testing purposes - still unable to get out to community.spiceworks.com<\/a><\/p>\n Any ideas on where I should go next? What I should look for? I am about out of ideas at the moment…<\/p>\n *Edits - revised info and fixed typos<\/p>","upvoteCount":4,"answerCount":8,"datePublished":"2018-05-30T11:50:46.000Z","author":{"@type":"Person","name":"nickdaszkiewicz","url":"https://community.spiceworks.com/u/nickdaszkiewicz"},"acceptedAnswer":{"@type":"Answer","text":" The issues did begin a few weeks ago but were intermittent, could never really diagnose the problem before it came back online - today was the first time it was down for more than a few minutes.<\/p>\n I reached out to our organizations technical contact at our ISP and he found a routing issue after one of the gateways. We have an SD-WAN implementation that utilizes a gateway on the ISP’s edge to determine best route between our sites. one of these routes was essentially dead ending. Because our SD-WAN constantly updates the route to the most efficient path, it explains the intermittent connectivity.<\/p>\n All in all L0ST_0NE’s hunch about ISP issues turned out to be right! Thanks again!<\/p>\n @l0st0ne<\/a><\/p>","upvoteCount":0,"datePublished":"2018-05-30T17:05:25.000Z","url":"https://community.spiceworks.com/t/unable-to-access-community-spiceworks/654282/7","author":{"@type":"Person","name":"nickdaszkiewicz2","url":"https://community.spiceworks.com/u/nickdaszkiewicz2"}},"suggestedAnswer":[{"@type":"Answer","text":" I fully expect the issues to be buried in my network, but as I inherited a completely undocumented network not more than a few months ago, finding the issue has proven difficult and the typical troubleshooting and fact finding steps have shown me little. Which brings me to this community from another network (phone hotspot) to ask for some help in identifying the issue.<\/p>\n So here we go!<\/p>\n I punch in community.spiceworks.com<\/a> into a brower and I get connection timed out errors in IE/Chrome/Edge<\/p>\n I do an nslookup and community.spiceworks.com<\/a> resolves to:<\/p>\n Name: 6396l.x.incapdns.net<\/a> I ping community.spiceworks.com<\/a>, 6396l.x.incapdns.net<\/a>, and 45.60.101.212 - all successfully<\/p>\n I run tracert, and route to our core switch, ASA, and then out to the ISP, various hops across the internet and eventually make it to the destination<\/p>\n We have an iBoss web filter, I put it in bypass and got the same results. To ensure it wasnt the iBoss, I grabbed a patch cable and took the iBoss out of the loop - no change<\/p>\n I checked firewall rules on several PCs and even outright disabled the firewall and antivirus software for testing purposes - still unable to get out to community.spiceworks.com<\/a><\/p>\n Any ideas on where I should go next? What I should look for? I am about out of ideas at the moment…<\/p>\n *Edits - revised info and fixed typos<\/p>","upvoteCount":4,"datePublished":"2018-05-30T11:50:46.000Z","url":"https://community.spiceworks.com/t/unable-to-access-community-spiceworks/654282/1","author":{"@type":"Person","name":"nickdaszkiewicz","url":"https://community.spiceworks.com/u/nickdaszkiewicz"}},{"@type":"Answer","text":" I could be a routing issue with your ISP. I had a similar issue were I couldn’t get to www.spiceworks.com<\/a> but could get to community.spiceworks.com<\/a> through our primary ISP (Spectrrum), but the back ISP had no issue getting to either.<\/p>\n It could also have something to do with the server moves that Spicework’s has been doing.<\/p>\n You can also look at this thread: I cannot download spiceworks application<\/a><\/p>\n
\nAddress: 45.60.101.212<\/p>\n
\nAddress: 45.60.101.212<\/p>\n