Re: IP to www

2003-12-20 Thread Kevin Mark
On Sat, Dec 20, 2003 at 01:46:29AM -0800, Vineet Kumar wrote: > * Gruessle ([EMAIL PROTECTED]) [031219 19:36]: > > > > > > From: Vineet Kumar [mailto:[EMAIL PROTECTED] > Looks like your ISP blocks port 80. Boneheads. I'd switch to a > different ISP, if it's feasible. Even though it's perfectl

Re: IP to www

2003-12-20 Thread Vineet Kumar
* Gruessle ([EMAIL PROTECTED]) [031219 19:36]: > > > From: Vineet Kumar [mailto:[EMAIL PROTECTED] > > * Gruessle ([EMAIL PROTECTED]) [031219 16:16]: > > > My router has a Firewall and the only port I have opened up > > is port 80 > > > Could it be that my cable company is blocking something? > >

RE: IP to www

2003-12-20 Thread John Smith
Hi Gruessle, step by step testing is easiest by using 'telnet ip-address port', this even works with windows ;-) start from within your local net 'telnet webservers-internal-address 80'. You should at least get a 'Connected' message. This confirms your web server is actually up. (Try testing

RE: IP to www

2003-12-19 Thread Eric Walstad
On Friday 19 December 2003 18:24, [EMAIL PROTECTED] wrote: > From: Vineet Kumar [mailto:[EMAIL PROTECTED] > > > * Gruessle ([EMAIL PROTECTED]) [031219 15:07]: > > > From: Vineet Kumar > > > > > > > http://68.68.202.34/ doesn't work for me. Of course, > > > > neither does a > > > > > > ping to tha

RE: IP to www

2003-12-19 Thread Gruessle
From: Vineet Kumar [mailto:[EMAIL PROTECTED] > * Gruessle ([EMAIL PROTECTED]) [031219 16:16]: > > My router has a Firewall and the only port I have opened up > is port 80 > > Could it be that my cable company is blocking something? > > I can't imagine how thou. > > Yes, it's possible that they co

Re: IP to www

2003-12-19 Thread Monique Y. Herman
On Sat, 20 Dec 2003 at 01:54 GMT, Gruessle penned: > > How do you do that I mean doesn't http allways come in from port 80 I > just shot off my firewall and it still does not work. > Port 80 is the default, so if you don't specify a port, that's what you'll get. To use a different port, do some

RE: IP to www

2003-12-19 Thread Gruessle
From: Jiele [mailto:[EMAIL PROTECTED] > Gruessle wrote: > > > > > > From: Vineet Kumar [mailto:[EMAIL PROTECTED] > > > >>* Gruessle ([EMAIL PROTECTED]) [031219 15:07]: > >> > >>> > >>>From: Vineet Kumar > >>> > http://68.68.202.34/ doesn't work for me. Of course, > >> > >>neither does a > >>

Re: IP to www

2003-12-19 Thread Vineet Kumar
* Gruessle ([EMAIL PROTECTED]) [031219 16:16]: > My router has a Firewall and the only port I have opened up is port 80 > Could it be that my cable company is blocking something? > I can't imagine how thou. Yes, it's possible that they could definitely be filtering tcp port 80 (or really any other

Re: IP to www

2003-12-19 Thread Jiele
Gruessle wrote: From: Vineet Kumar [mailto:[EMAIL PROTECTED] * Gruessle ([EMAIL PROTECTED]) [031219 15:07]: From: Vineet Kumar http://68.68.202.34/ doesn't work for me. Of course, neither does a ping to that address, or a tracepath. Are you sure that's your address? My IP I checked at http:

RE: IP to www

2003-12-19 Thread Gruessle
From: Vineet Kumar [mailto:[EMAIL PROTECTED] > * Gruessle ([EMAIL PROTECTED]) [031219 15:07]: > > > > > > From: Vineet Kumar > > > http://68.68.202.34/ doesn't work for me. Of course, > neither does a > > > ping to that address, or a tracepath. Are you sure that's > > > your address? > > > > M

RE: IP to www

2003-12-19 Thread Gruessle
From: Ken Gilmour [mailto:[EMAIL PROTECTED] > > On Fri, 19 Dec 2003 15:11:24 -0800, Gruessle wrote: > > > > > > From: Kent West [mailto:[EMAIL PROTECTED] > >> Gruessle wrote: > >> > >> > >>> I know what my given IP address is. Given by my cable company. > >>> IP 68.68.202.34 > >>> Also I have ope

RE: IP to www

2003-12-19 Thread Ken Gilmour
On Fri, 19 Dec 2003 15:11:24 -0800, Gruessle wrote: > > > From: Kent West [mailto:[EMAIL PROTECTED] >> Gruessle wrote: >> >> >>> I know what my given IP address is. Given by my cable company. >>> IP 68.68.202.34 >>> Also I have opened up port 80 on my Siemens routers firewall. >>> >>> >>> Private I

Re: IP to www

2003-12-19 Thread Vineet Kumar
* Gruessle ([EMAIL PROTECTED]) [031219 15:07]: > > > From: Vineet Kumar > > http://68.68.202.34/ doesn't work for me. Of course, neither does a > > ping to that address, or a tracepath. Are you sure that's > > your address? > > My IP I checked at http://checkip.dyndns.org/, so this should be r

RE: IP to www

2003-12-19 Thread Gruessle
From: Kent West [mailto:[EMAIL PROTECTED] > Gruessle wrote: > > >I know what my given IP address is. Given by my cable company. > >IP 68.68.202.34 > >Also I have opened up port 80 on my Siemens routers firewall. > > > >Private IP: 192.168.254.225 > >Private Port: 80 > >Type: TCP > >Public Port: 8

RE: IP to www

2003-12-19 Thread Gruessle
From: Vineet Kumar > * Gruessle ([EMAIL PROTECTED]) [031219 13:03]: > > > > > > From: Rus Foster [mailto:[EMAIL PROTECTED] > > > > > > > > That might be the problem how do I check that? > > > > > > > > (To Rus: Sorry for sending this at first direct to your > > > email address > > > > Rus) > > >

Re: IP to www

2003-12-19 Thread Kent West
Gruessle wrote: I know what my given IP address is. Given by my cable company. IP 68.68.202.34 Also I have opened up port 80 on my Siemens routers firewall. Private IP: 192.168.254.225 Private Port: 80 Type: TCP Public Port: 80 But when I enter the 68.68.202.34 ip in a browser it does not work. Wh

Re: IP to www

2003-12-19 Thread Vineet Kumar
* Gruessle ([EMAIL PROTECTED]) [031219 13:03]: > > > From: Rus Foster [mailto:[EMAIL PROTECTED] > > > > > > That might be the problem how do I check that? > > > > > > (To Rus: Sorry for sending this at first direct to your > > email address > > > Rus) > > > > Just try putting http://192.168.254.2

RE: IP to www

2003-12-19 Thread Gruessle
From: Rus Foster [mailto:[EMAIL PROTECTED] > > > > That might be the problem how do I check that? > > > > (To Rus: Sorry for sending this at first direct to your > email address > > Rus) > > Just try putting http://192.168.254.254 in a browser > > Rus > Like I sad that just takes me to my router

RE: IP to www

2003-12-19 Thread Rus Foster
> > That might be the problem how do I check that? > > (To Rus: Sorry for sending this at first direct to your email address > Rus) Just try putting http://192.168.254.254 in a browser Rus -- e: [EMAIL PROTECTED] | Linux + FreeBSD Servers from $12.50/mo e: [EMAIL PROTECTED] | Full Roo

RE: IP to www

2003-12-19 Thread Gruessle
From: Rus Foster [mailto:[EMAIL PROTECTED] > On Fri, 19 Dec 2003, Gruessle wrote: > > > > Private IP: 192.168.254.225 > > Private Port: 80 > > Type: TCP > > Public Port: 80 > > > > That looks ok. Is the webserver actually listening on 192.168.254.225? > > Rus That might be the problem how do I ch

Re: IP to www

2003-12-19 Thread Joseph A. Nagy
On Friday 19 December 2003 01:04 pm, Rus Foster wrote: > On Fri, 19 Dec 2003, Gruessle wrote: > > Private IP: 192.168.254.225 > > Private Port: 80 > > Type: TCP > > Public Port: 80 > > That looks ok. Is the webserver actually listening on > 192.168.254.225? > > Rus > -- > w: http://www.jvds.com |

Re: IP to www

2003-12-19 Thread Rus Foster
On Fri, 19 Dec 2003, Gruessle wrote: > > Private IP: 192.168.254.225 > Private Port: 80 > Type: TCP > Public Port: 80 > That looks ok. Is the webserver actually listening on 192.168.254.225? Rus -- w: http://www.jvds.com | JVDS Tech Channel: e: [EMAIL PROTECTED]| http://tech.jvds.com t: