Recommandations..

[IchBin]

Sorry to ask this here but does anyone have a recommendations for a
network newsgroup out there.

I am having major problem with my website. No one can get to it. I run
Apache and Tomcat on a windoze XP SP Home edition. I have looked at
everything. My dynamic address is mapped and maintained to a domain name
weconsultants.servebeer.com

Even when I surf the Internet a lot of pages come up with "Not Found
messages and the apache signature for me. The ads you see on the margins
of a page. It does not make sense. I have eliminated apache and the
domain name and have people come in with my IP address and port 8080 to
no avail... Even taking my firewall down. I can traceroute hops from a
remote address to my dynamic address. Just unbelievable.


Thanks in Advance...
IchBin, Pocono Lake, Pa, USA
http://weconsultants.servebeer.com/JHackerAppManager
__________________________________________________________________________

'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor, Regular Guy (1952-)

 

[Chris Uppal]

Sorry to ask this here but does anyone have a recommendations for a
network newsgroup out there.

Your problems sound very ISP specific; if you haven't already done so then it
would be worth checking whether they have some sort of support forum or user
forum.

You could even try their support line, if you're that desperate ;-) (Check
that you are allowed to run a HTTP server from your type of account first !)

FWIW I can reach port 8080 at weconsultants.servebeer.com with no obvious
problems, but there is no response of any kind (just a black hole at the IP
level) to packets going to port 80.

-- chris

 

[IchBin]

Your problems sound very ISP specific; if you haven't already done so then it
would be worth checking whether they have some sort of support forum or user
forum.

You could even try their support line, if you're that desperate ;-) (Check
that you are allowed to run a HTTP server from your type of account first !)

FWIW I can reach port 8080 at weconsultants.servebeer.com with no obvious
problems, but there is no response of any kind (just a black hole at the IP
level) to packets going to port 80.

-- chris

Thanks Chris for your response. I would think that it is the ISP. I have
talked to them and they say it is my software or hardware that is the
problem not them. So I did look at the ISP policy and they do not like
people running servers off the users pc's that is I guess making a
dynamic IP address to look like a static one. So not sure if I can rely
on their answer. Which leads me to think that they are stopping any
unsolicited IP packets. I am looking at the firewall logs to verify that.

That said, their are two things that bother me. I can not traceroute
from a remote location with the windoze firewall up. It takes me to one
hope before my IP address. It stops at my ISP. If I take down the
firewall I can traceroute to my dynamic IP address which
is mapped to weconsultants.servebeer.com If they were filtering my ports
I figure think that it would not matter if the firewall was up or down?
Sorry not sure what port address the traceroute get a ACK from. Figured
it would be port 80. Been some time since I have looked at network
stuff. I am assuming that it is a TCP and not UDP or ICMP. I am not
seeing a lot of OPEN-INBOUND records.

I have added 80 and 8080 as exceptions for the firewall but it does not
matter. My next test is to load in zone alarm and take MS firewall out
of the picture and see what happens. I know ports 80 and 8080 are
Listening for incoming packets.

Also as of late my pc just hangs every now and again. Have not pin
pointed it yet. The apps that are running are ok but can not doing
anything out side of them except to bring up the task manager else
hourglass. I have to log off and log back on again to clear up.

When you said you have no problem with 8080 how are you accessing that
port. You can bring up the site by doing
weconsultants.servebeer.com:8080? It is hard being I am on the target pc
for testing.

With firewall UP: (Traceroute from University of Washington )

1 acar-ads-02-vlan190.cac.washington.edu (140.142.3.3) 0 ms 1 ms 0 ms
2 uwbr-ads-01-vl1998.cac.washington.edu (140.142.155.23) 2 ms 0 ms 1 ms
3 prs1-wes-ge-0-0-0-0.pnw-gigapop.net (209.124.176.5) 1 ms 1 ms 1 ms
4 att-pwave-1.peer.pnw-gigapop.net (209.124.179.41) 1 ms 0 ms 1 ms
5 12.127.6.102 (12.127.6.102) 63 ms 64 ms 69 ms
6 tbr2-cl11.cgcil.ip.att.net (12.122.10.61) 78 ms 66 ms 68 ms
7 tbr1-cl22.cgcil.ip.att.net (12.122.9.133) 64 ms 64 ms 64 ms
8 tbr1-cl14.n54ny.ip.att.net (12.122.10.1) 63 ms 74 ms 63 ms
9 12.122.84.69 (12.122.84.69) 67 ms 117 ms 75 ms
10 gateway2-pos1-1.str.ptd.net (12.119.12.70) 73 ms 73 ms 92 ms
11 gateway-g1-0-0.cmts.mtp.ptd.net (204.186.5.34) 80 ms 73 ms 77 ms
*
*
does not return..

With firewall down:

1 acar-ads-02-vlan190.cac.washington.edu (140.142.3.3) 0 ms 1 ms 0 ms
2 uwbr-ads-01-vl1998.cac.washington.edu (140.142.155.23) 1 ms 1 ms 0 ms
3 prs1-wes-ge-0-0-0-0.pnw-gigapop.net (209.124.176.5) 1 ms 0 ms 1 ms
4 att-pwave-1.peer.pnw-gigapop.net (209.124.179.41) 1 ms 0 ms 1 ms
5 12.127.6.102 (12.127.6.102) 68 ms 77 ms 62 ms
6 tbr2-cl11.cgcil.ip.att.net (12.122.10.61) 76 ms 76 ms 71 ms
7 tbr1-cl22.cgcil.ip.att.net (12.122.9.133) 64 ms 65 ms 91 ms
8 tbr1-cl14.n54ny.ip.att.net (12.122.10.1) 424 ms 69 ms 62 ms
9 12.122.84.69 (12.122.84.69) 168 ms 137 ms 188 ms
10 gateway2-pos1-1.str.ptd.net (12.119.12.70) 73 ms 73 ms 145 ms
11 gateway-g1-0-0.cmts.mtp.ptd.net (204.186.5.34) 73 ms 85 ms 124 ms
12 24.229.218.58.res-cmts.mtp.ptd.net (24.229.218.58) 86 ms 88 ms 79 ms


Thanks in Advance...
IchBin, Pocono Lake, Pa, USA
http://weconsultants.servebeer.com/JHackerAppManager
__________________________________________________________________________

'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor, Regular Guy (1952-)

 

[Chris Uppal]

That said, their are two things that bother me. I can not traceroute
from a remote location with the windoze firewall up. It takes me to one
hope before my IP address.

IIRC tracert uses ICMP ping packets, which may well be handled differently from
TCP packets on port 80. From here I can (at 13:48 UCT, 2006-05-11) ping all
the way to your machine. So nothing's blocking that. I'd guess that your
firewall would (by default) refuse ping packets (that's a fairly normal
security choice for private machines -- it doesn't make nearly as much sense
for machines which are intended to be available to the Net at large). So maybe
your firewall is not currently active (I /think/ I remember that ping was
blocked at your machine when I posted earlier).

But that doesn't tell us much about where TCP over port 80 is going wrong. I
can connect normally to port 8080, but get nothing on port 80[*]. I actually
got a ICMP "destination unreachable" response coming from IP 204.186.5.34, with
reason code 13 ("administratively filtered"). That IP is the last hop before
your own machine. My /guess/ is that your ISP is blocking my attempt to
connect to you. That seems a reasonable guess if your own setup treats ports
80 and 8080 the same way.

Also as of late my pc just hangs every now and again.

Not wanting to sound too alarmist, but with all the time you've spent without
an active firewall, is it possible that someone has owned your machine.

When you said you have no problem with 8080 how are you accessing that
port. You can bring up the site by doing weconsultants.servebeer.com:8080?

Yup, that works fine.

-- chris

([*] at exactly 13:52:30 UTC in case you want to check your logs)