Re: Weird connection issues...
From: Kristofer Gafvert (kgafvert_at_NEWSilopia.com)
Date: 12/06/04
- Next message: Kristofer Gafvert: "Re: Unexpected login screen"
- Previous message: Bernard: "Re: Weird connection issues..."
- In reply to: Kevin Grigorenko: "Re: Weird connection issues..."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 6 Dec 2004 09:20:34 +0100
Hello Kevin,
> Wow, you're right. I also can't ping, is that being blocked as well (I
> honestly don't know how ping even works, is that through a specific
> port?)?
Ping can be blocked by your firewall/router, or by your ISP. Simply said,
the device does not answer on a ping request, and that is why you cannot
ping it.
> Anyway, this is so dumb, why would they block 80 and not block my SMTP
> server? I would think that's more potentially damaging.
ISPs block ports by many reasons. The most commons are that they do not want
you to run a server without paying extra. And for blocking port 25, they do
not want their IP range to end up on email server's black lists.
> Is there any way around this without paying for hosting, or do I have to
> just deal with my ISP?
You have probably signed a paper that you will not run a server, so you will
probably break some rule. If I were you, I would contact the ISP and ask
them if I could run the webserver (they will probably not allow SMTP) as a
"personal server" (only you and your friends will use it). Some ISPs allow
this. They might unblock port 80 for you in this case, or you can run it on
another port. If you do not want to type in the port number when browsing
the website, there are free (or commercial) services for that. Dyndns.org
offers something called MyWebHop which can redirect requests on port 80 to
another port on your webserver.
Link:
http://www.dyndns.org/services/mywebhop/
Hope this answers all your questions and gives you a solution for solving
your problem.
Good Luck!
-- Regards, Kristofer Gafvert http://www.ilopia.com "Kevin Grigorenko" <KevinGrigorenko@discussions.microsoft.com> wrote in message news:BE04E4C6-4176-4A3D-A1D3-88D6F937CFF5@microsoft.com... > Wow, you're right. I also can't ping, is that being blocked as well (I > honestly don't know how ping even works, is that through a specific > port?)? > Anyway, this is so dumb, why would they block 80 and not block my SMTP > server? I would think that's more potentially damaging. > > Is there any way around this without paying for hosting, or do I have to > just deal with my ISP? > > Thanks, > Kevin Grigorenko > > "Bernard" wrote: > >> It could be ISP blocking port 80 traffic. >> can you 'telnet yourip 80' ? >> >> if you get 'connection can not be established' meaning port 80 is not >> reachable. >> change it to 8080 or something else to test first. >> >> -- >> Regards, >> Bernard Cheah >> http://www.tryiis.com/ >> http://support.microsoft.com/ >> http://www.msmvps.com/bernard/ >> >> >> >> "Kevin Grigorenko" <KevinGrigorenko@discussions.microsoft.com> wrote in >> message news:ECAD8AD5-12E5-46A0-8692-6AE6547DBD20@microsoft.com... >> > Hello all, >> > >> > I've just finished setting up a full Windows Server 2003 environment. >> > Got >> > Active Directory working and DNS (after a while). My setup is a dsl >> > connection into a Linksys router. There is one server which hosts >> everything >> > (IIS, Exchange, DC, etc.) on the LAN and two client computers which are >> > irrelevant. They are actually not on the domain yet, which will come >> > into >> > the picture later. >> > >> > In my router, I've got ports 0-10000 forwarding to my server (for >> > testing >> > purposes, I'll narrow down the ones I need later :)). Now, since I >> > have a >> > dynamic IP, I'm using zoneedit.com to publish my IP to zoneedit, and to >> which >> > I point my website's name servers. zoneedit then points to my IP and >> > has >> mx >> > records, etc. >> > >> > When I was just at home setting everything up, everything worked fine. >> > I >> > used my other two computers, which were not on the domain and did not >> > have >> my >> > server as a DNS setting in their IP settings, and they could ping and >> > do >> > everything fine. The comps were going to my ISP's DNS, so I know that >> they >> > weren't finding my site just throught the LAN. >> > >> > Now I'm back to college, but none of my pages work!! What's weird is >> > that >> > FTP works, and I can use Remote Desktop too, which is good in a way >> > since >> I >> > can fiddle with my server, but is baffling at the same time. >> > >> > Do I have to do something with ACLs or user setup to allow port 80 >> traffic? >> > I was thinking about putting my server on the DMZ on my router, but >> > that >> > seems bad. Also, I'm not using any UPnP forwarding in my router, but i >> tried >> > forwarding upnp port 80 as well as my normal forwarding and it still >> didn't >> > work. >> > >> > The IIS server is working fine because I can remote desktop in to my >> server >> > and I can locally go to the site. Also, ftp is working which is hosted >> > by >> > iis. >> > >> > Moreover, when I ping my domain name, it resolves to the correct IP, >> > but >> the >> > ping packets fail. This must have something to do with the problem. >> > >> > Thank you so much! >> > Kevin Grigorenko >> >> >>
- Next message: Kristofer Gafvert: "Re: Unexpected login screen"
- Previous message: Bernard: "Re: Weird connection issues..."
- In reply to: Kevin Grigorenko: "Re: Weird connection issues..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
