[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Qube3 - behind a router, behind a router...
- Subject: RE: [cobalt-users] Qube3 - behind a router, behind a router...
- From: "Earl" <earl@xxxxxxxxxxxxxxxx>
- Date: Fri Sep 20 08:32:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Thanks for the answer.. I finally figured it out late last night.
The httpd.conf file had a number of Listen statements, still using the
external IP. They needed to be changed to the internal IP address..
Thanks,
Earl
-----Original Message-----
From: Gareth Bromley [mailto:gbromley@xxxxxxxxxxx]
Sent: Friday, September 20, 2002 7:33 AM
To: earl@xxxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] Qube3 - behind a router, behind a router...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Earl wrote:
| I have an ADSL line with a CISCO 800 router. I don't have
access to
| configure this router, so I had someone configure another
router for me,
| a CISCO 1605R, that was to be placed between the CISCO 800
and my hub.
|
| The Qube3 was given an internal IP, and the router was
configured to
| send requests to the static ip, to this internal IP.
Using what? NAT on the 1605R router?
Whats your networking addressing scheme/subnets in use? Hows the router
connect the two networks? By routing or bridging? etc...
| It works fine for an NT server, but the Qube's web/ftp
service doesn't
| respond. I can successfully ping the Qube3 internal IP
and I can access
| the configuration page on port 444, but I can't get access
to the web
| page.
What are the NAT statements on the router? is FTP/Web still bound to ht
NT server? If so the RaQ will never until the NAT statements are
unbound.
How do you know you are pinging the Qube?
| Does anyone have an idea of what's happening?
Do you have access to the 1605R router? If so a copy of the config would
help for starters.
Do you have tcpdump on the Qube? If so us it to traffic dump
~ requests to you using:
tcpdump tcp port 80
To see all web traffic trying to connect. If you see traffic hit, but
from the client dont see the reply check the folowing:
- - Default gateway on Qube is correct
- - Subnet mask on Qube is correct
- - The outbound/firewalling ACLs allow return traffic back through the
1605R router
If you dont see any taffic hit via tcpdump, then do a
similar thing on the router using debug ip packet ACLNumber where
ACLNumber is an access-list detailing the traffic you are watching i.e.
access-list 110 permit tcp any host externalIP eq 80
debug ip packet 110
I think we all need more info, before a resolution can be found.
- --
- --Gareth Bromley
CCIE Candidate CCDP CCNP CSS1 CCIP Security
CCSA CCSE NSA RHCE SCSA CISSP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9iweHxX2wgg94RlkRAqjSAJ9QkN1azbLsnBTFyfzIX0ytc+FVSgCguI2j
NkSq5cRzgqhFCWe2b3GOias=
=B/wF
-----END PGP SIGNATURE-----