[SOLVED] Unable to access port 8008 from web browser

NirvanaBaby · 01-22-2011, 08:08 PM

So this is my first post so I'll put it in "Newbie". I seem to have successfully configged my httpd.conf file to listen on port 8008. I restarted httpd ok. However, when I go to port 8008 in a web browser from another computer on the internal network by going to 192.168.2.5:8008, it doesn't connect. When listening on port 80, I can browse to the IP address fine. is this a server-side or client-side issue? Using Fedora 12. Thanks in advance and tell me what forum this would best fit in.

frankbell · 01-22-2011, 08:39 PM

If there's a firewall, is port 8008 open in the firewall?

NirvanaBaby · 01-22-2011, 09:08 PM

frankbell,
I'm trying to access from another computer on the internal network. The firewall on my Belkin should be irrelevant, right? There is selinux to consider though...?

frankbell · 01-22-2011, 09:29 PM

Correct.

I was thinking of a software firewall on the local computer.

jobslocaltech · 01-22-2011, 10:11 PM

Try telnet IP port

NirvanaBaby · 01-27-2011, 10:32 AM

(Deleted this post)

NirvanaBaby · 01-27-2011, 10:48 AM

jobslocaltech, I follow you. Yeah, I can telnet to that port (now 488) on that IP but only FROM the computer running apache. also, i can bring it up in a browser. However, telnetting to that ip and port from another (Windows) computer merely returns to a c:> prompt with no error.

szboardstretcher · 01-27-2011, 10:51 AM

Quote:

Originally Posted by NirvanaBaby

jobslocaltech, I follow you. Yeah, I can telnet to that port (now 488) on that IP but only FROM the computer running apache. also, i can bring it up in a browser. However, telnetting to that ip and port from another (Windows) computer merely returns to a c:> prompt with no error.

I would *temporarily* disable iptables on the web server and try connecting to it again.

Code:

service iptables stop

try to connect from remote. then to re-enable

Code:

service iptables start

nicktickson122 · 01-27-2011, 12:40 PM

I can telnet to that port (now 488) on that IP but exclusive FROM the computer running athapascan. also, i can transport it up in a application. However, telnetting to that ip and port from other (Windows) computer simply returns to a c:> prompt with no evil.

szboardstretcher · 01-27-2011, 12:42 PM

Quote:

Originally Posted by nicktickson122

I can telnet to that port (now 488) on that IP but exclusive FROM the computer running athapascan. also, i can transport it up in a application. However, telnetting to that ip and port from other (Windows) computer simply returns to a c:> prompt with no evil.

To be clear on this: You disabled IPtables on the web server, and tried to connect from a windows machine, and it did not work? But, you can connect to the webserver when it is set up on port 80?

theNbomr · 01-27-2011, 03:48 PM

Set up a packet sniffer (wireshark), and see if there is any traffic received on the port(s) of interest.
As root, run at a bash commandline:

Code:

for table in filter nat mangle; do iptables -t $table -L; done

See if there is a rule blocking traffic on port 8008.

Use netcat (nc) to set up a listener on the port of interest, and try to connect with it from other clients (browsers, etc.).

Code:

nc -l 8008

Observe results, and report as necessary.
--- rod.

NirvanaBaby · 01-27-2011, 04:43 PM

Quote:

Originally Posted by nicktickson122

I can telnet to that port (now 488) on that IP but exclusive FROM the computer running athapascan. also, i can transport it up in a application. However, telnetting to that ip and port from other (Windows) computer simply returns to a c:> prompt with no evil.

nicktickson122, your post was almost identical to mine. are you having the same issue? If so, tell me if you fix it. i'll try shutting off iptables when i get home.