Re: Can't access NEWS.CIS.DFN.DE

From: leslie (LESLIE_at_JRLVAX.HOUSTON.RR.COM)
Date: 09/17/03

  • Next message: Dan Ferris: "Re: SSH root exploit in the wild - Patches available." 
    Date: Wed, 17 Sep 2003 20:41:05 GMT

    Jackeline D (jenny@invalid.com) wrote:
    : I am in the UK and I have recently installed cable broadband using
    : NTL.
    :
    : I use Xnews as my newsreader and I find that I can access any of my
    : usual news servers but for some reason I can not access
    : NEWS.CIS.DFN.DE (or its recent new name of NEWS.INDIVIDUAL.NET).
    :
    : (1) If I dial up to another ISP (Freeserve) then I *can* read and
    : write to NEWS.CIS.DFN.DE.
    :
    : (2) However if I drop the dialup line and then re-connect my cable
    : modem and allo wit to work then I find I can *not* access
    : NEWS.CIS.DFN.DE.
    :
    : (3) If I then dial up using Virgin (which uses NTL's networks) then
    : I find I can *not* access it.
    :
    : NTL may be the problem. How can I access the NEWS.CIS.DFN.DE
    : newsserver when connected via NTL?
    :
    : For my firewall I use Sygate Personal Pro 5. I get these same
    : results above if I disable Sygate. Am I disabling it fully? I
    : rightclick the small icon and select "exit". Other times I just
    : rightclick and select "allow all". Is this sufficient to disable it?
    :
    : Can anyone advise please.
    :

    While connected to NTL, open a DOS command window and ping
    NEWS.INDIVIDUAL.NET. The results should look like this:

      C:\>ping NEWS.INDIVIDUAL.NET

      Pinging NEWS.INDIVIDUAL.NET [130.133.1.4] with 32 bytes of data:

      Reply from 130.133.1.4: bytes=32 time=194ms TTL=233
      Reply from 130.133.1.4: bytes=32 time=193ms TTL=233
      Reply from 130.133.1.4: bytes=32 time=192ms TTL=233
      Reply from 130.133.1.4: bytes=32 time=192ms TTL=233

      Ping statistics for 130.133.1.4:
          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
          Minimum = 192ms, Maximum = 194ms, Average = 192ms

      C:\>

    If the ping command comes back with an "Unknown host" error, then
    the problem is with NTL's DNS servers.

    You can use public DNS servers instead, from one of these sites:

        http://dns.widge.net/
        Free DNS, Managed DNS, Backup DNS, web-based zone manager at dns.widge.net

        http://www.opennic.unrated.net/public_servers.html
        OpenNIC: Public Name Servers

        http://www.granitecanyon.com/
        The Public DNS Service

        http://support.open-rsc.org/.servers/
        ORSC Public Access DNS Nameservers

    --Jerry Leslie
      Note: leslie@jrlvax.houston.rr.com is invalid for email

  • Next message: Dan Ferris: "Re: SSH root exploit in the wild - Patches available."

    Relevant Pages

    • Re: Cant access NEWS.CIS.DFN.DE
      ... NTL may be the problem. ... > then the problem is with NTL's DNS servers. ... > You can use public DNS servers instead, ...
      (comp.security.misc)
    • Re: Cant access NEWS.CIS.DFN.DE
      ... NTL may be the problem. ... > then the problem is with NTL's DNS servers. ... > You can use public DNS servers instead, ...
      (comp.security.firewalls)
    • Re: Cant access NEWS.CIS.DFN.DE
      ... NTL may be the problem. ... You can use public DNS servers instead, ...
      (comp.security.firewalls)
    • Re: Exchange 2000 on company.local domain
      ... > I've been told by SBC that I will be managing my own DNS. ... That's fine for your internal network, but you do not want to host your own ... You'd need two DNS servers, ... Have someone else host your public DNS - if SBS won't do it, ...
      (microsoft.public.exchange2000.connectivity)
    • Re: FQDN vs Domain DNS name error
      ... set to the NetBIOS name of the server vs the public DNS name. ... click "Configure external DNS servers"? ... provides your circuit) needs to create/edit PTRs - and they may ...
      (microsoft.public.exchange.admin)