Post #39,573
5/22/02 10:34:51 PM
|
Done
and the server is restarting now just to be sure.
I am free now, to choose my own destiny.
|
Post #39,579
5/22/02 11:27:35 PM
5/22/02 11:31:34 PM
|
Well, it still doesn't work...
So I port-scanned you. Here are the results: Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ )
Interesting ports on dsl-64-129-13-109.telocity.com (64.129.13.109):
(The 1539 ports scanned but not shown below are in state: filtered)
Port State Service
110/tcp closed pop-3
113/tcp closed auth
8080/tcp closed http-proxy
Nmap run completed -- 1 IP address (1 host up) scanned in 154 seconds
Imric's Tips for Living- Paranoia Is a Survival Trait
- Pessimists are never disappointed - but sometimes, if they are very lucky, they can be pleasantly surprised...
- Even though everyone is out to get you, it doesn't matter unless you let them win.
Edited by imric
May 22, 2002, 11:31:34 PM EDT
|
Post #39,605
5/23/02 9:58:39 AM
|
What make/model router?
~~~)-Steven----
"I want you to remember that no bastard ever won a war by dying for his country.
He won it by making the other poor dumb bastard die for his country..."
General George S. Patton
|
Post #39,673
5/23/02 2:16:03 PM
|
Make model router
DLINK DI-804
I have them on tech support by email. Told them I applied the latest firmware, they emailed me back to try the latest firmware upgrade. Duh! Jeff Daniels and Jim Carey must be running their helpdesk?
I am free now, to choose my own destiny.
|
Post #39,715
5/23/02 6:11:53 PM
|
troubleshooting
I looked at the manual for that model. It doesn't look like that router allows you to set up your own packet filters. I guess I just assumed it did. You'll definately want to set up a firewall on your server if there is no packet filter on the router. I've included a checklist of troubleshooting questions, please don't feel insulted by the simplicity of some of them, sometimes we all miss the little things.
Is the DHCP server enabled on the router?
-Yes
--Did you reserve the server's IP address in the DHCP Server Settings?
--Is your server set up as a DHCP client?
--You might also try disabling DHCP and setting up your server with a static IP (see below)
-No
--Did you manually set the DNS addresses of your ISP on your server?
Does your ISP for some reason block that port (and others)? They don't normally, but it is possible.
~~~)-Steven----
"I want you to remember that no bastard ever won a war by dying for his country.
He won it by making the other poor dumb bastard die for his country..."
General George S. Patton
|
Post #39,806
5/24/02 10:49:44 AM
|
Re: troubleshooting
I set up the server with the static IP 192.168.0.2 and used the ISP's DNS settings. I followed all those steps, and either the ISP is blocking port 80, or this router needs some other settings?
I am free now, to choose my own destiny.
|
Post #39,854
5/24/02 4:09:04 PM
|
Have you looked at
The Intrusion Detection Log? Both Imric and I have tried port scans on your IP, these should have shown up on this log if they made it to your router.
Another thing you can try is connecting your server directly to the DSL modem. See if your web server shows up then. You should probably have Black Ice running to protect yourself, just make sure you can open up port 80. Also make sure your security updates are current.
~~~)-Steven----
"I want you to remember that no bastard ever won a war by dying for his country.
He won it by making the other poor dumb bastard die for his country..."
General George S. Patton
|
Post #39,857
5/24/02 5:05:07 PM
|
DSL or Cable?
either the ISP is blocking port 80
Verizon has done exactly this on the East Coast. Anyone that had DSL before the merger with GTE may not be blocked, but everyone else using Verizon ADSL is probably hosed.
I'd suggest switching to port 8080 and see if things magically start working.
|
Post #39,917
5/25/02 5:04:16 PM
|
DSL
DirectTV (I joined when they were Telocity). Do they bloack port 80? If so, they never told me that they did.
I am free now, to choose my own destiny.
|
