Can't connect to home server from church
-
Riley.Loader
- New Member
- Posts: 9
- Joined: Mon Jun 21, 2010 5:04 pm
- Location: USA, Utah, Orem
Can't connect to home server from church
Recently I've been playing with a server at my house, trying to get it ready for actual use with a few websites. I've been almost completely unable to connect to that server when on the church network. It just times out. Though I can connect to it anywhere else in the world. I was going to just give up on it, but suddenly I noticed that my android tablet (wifi) IS able to connect to the server. I'm thinking perhaps it might be that my android uses a different set of nameservers, but I can't even connect on the computer when just using the IP (currently 76.8.200.141). The domain is test.loaderfam.net, and I'm really puzzled. Anybody have any ideas as to what could be the reason?
-
russellhltn
- Community Administrator
- Posts: 34487
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Re: Can't connect to home server from church
The church uses a firewall. I'm not sure of all the rules.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
-
sbradshaw
- Community Moderators
- Posts: 6259
- Joined: Mon Sep 26, 2011 9:42 pm
- Location: Utah
- Contact:
Re: Can't connect to home server from church
Some firewalls block web sites that are accessed within a few days or weeks of being created, because that's a common characteristic of phishing sites (created and publicized quickly to imitate a bank, for example, then taken down before they're caught). This happened to me with one of my web sites [which was not a phishing site 
], which was blocked for a little while on BYU's firewall (Cisco, if I remember correctly).
], which was blocked for a little while on BYU's firewall (Cisco, if I remember correctly).Samuel Bradshaw • If you desire to serve God, you are called to the work.
-
Riley.Loader
- New Member
- Posts: 9
- Joined: Mon Jun 21, 2010 5:04 pm
- Location: USA, Utah, Orem
Re: Can't connect to home server from church
Good thought, something similar crossed my mind too. The ultimate hope is that it'll at least eventually clear. Though it's been a couple of weeks so far. You just had to wait it out for yours that was blocked on BYU's firewall?
-
russellhltn
- Community Administrator
- Posts: 34487
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Re: Can't connect to home server from church
I believe some firewalls block all IPs that are known to be home users.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
-
sbradshaw
- Community Moderators
- Posts: 6259
- Joined: Mon Sep 26, 2011 9:42 pm
- Location: Utah
- Contact:
Re: Can't connect to home server from church
I submitted a request to BYU IT and by the time they got around to it the problem had resolved itself. I don't remember exactly how long it took. So it was just a matter of waiting it out.
Samuel Bradshaw • If you desire to serve God, you are called to the work.
-
sbradshaw
- Community Moderators
- Posts: 6259
- Joined: Mon Sep 26, 2011 9:42 pm
- Location: Utah
- Contact:
Re: Can't connect to home server from church
Out of curiosity, was this ever resolved?
Samuel Bradshaw • If you desire to serve God, you are called to the work.
-
Riley.Loader
- New Member
- Posts: 9
- Joined: Mon Jun 21, 2010 5:04 pm
- Location: USA, Utah, Orem
Re: Can't connect to home server from church
Sorry, extremely late reply
A funny circumstance had me googling my domain name and this came up. I never realized you'd asked if it was resolved. It did eventually fix itself, yes.
A funny circumstance had me googling my domain name and this came up. I never realized you'd asked if it was resolved. It did eventually fix itself, yes.