[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Re: Newbie Q about webaliser :)
- Subject: Re: [cobalt-users] Re: Newbie Q about webaliser :)
- From: "paul" <paul@xxxxxxxxxxxxxxxxx>
- Date: Thu Jan 1 16:02:00 2004
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Oki... (and Jeff - thanks for your assistance on this one!)
The ip address coming into me is 82.32.145.19 - this is dynamic, and
Is forwarded by dns2go.com who host my domain names, and forward to me
through their dns2go forwarding service. This forwards to my Router, which
forward any requests in turn to port 80 through to this machine only. There
are other windows machines on the network, but ANYTHING that comes in on the
usual port suspects (21/25/80/110) is forwarded to the 4i.
When I try to ftp into the box, it recognises the ip change and changes the
ip that it tries to connect with to the local ip, so I guess that's why I
cant ftp into the box.Strangely enough it does connect, but cant receive the
listing - I think I can see why now!
I've now managed to fix the remote access into the box by allowing ports 81
and 444 through the firewall to point to this box - **hoorah!!**
Ummm...so I think the only problem I'm gonna have is ftp, which to my guess
is not a fixable one The only thing I can think of doing it to plonk it into
the DMZ (de-militarised zone), as that might work....
>> Status Message
>> Master DNS defined by SOA (d2gdns1.dns2go.com) was not found among NS
>> records.
>
>If you can get them to fix it, then do so, because...
>
>> Help
>> SOA record contains a name of master DNS server. This name you enter
>> on your DNS server. However, this name did not match any of DNS
>> servers, listed for your domain. Often this means that the server
>> name in SOA record is simply wrong. This can cause problem with
>> Windows 2000/XP computers in this domain, because Windows machines
>> use this name as a way to find master DNS.
>
>This could be a problem, but only for you, and only locally, and only if
>you're using W2K/XP computers on the same routable network.
>
>It really sounds like the ISP has blocked the port you're trying to
>connect through.
I'll inform them of this, tho whether anything will happen.....
Paul