Re: unknow tcp/ip problem

From: Maikel L. Miranda (admin_at_jovenclub.cu)
Date: 03/20/04

  • Next message: Maikel L. Miranda: "Re: unknow tcp/ip problem"
    To: <freebsd-isp@freebsd.org>
    Date: Sat, 20 Mar 2004 17:00:19 -0500
    
    

    It's done, the entire subnet is listed on my DNS tables (including the
    reverse) otherwise they coudn't access to POP service (which is in other
    server).
    Any other idea ?

    Thanks,
    Maikel L. Miranda.

    ----- Original Message -----
    From: "Cody Baker" <cody@wilkshire.net>
    To: "Maikel L. Miranda" <admin@jovenclub.cu>
    Sent: Saturday, March 20, 2004 4:42 PM
    Subject: Re: unknow tcp/ip problem

    > Perhaps you've already tried this, but I suspect it's hanging on the
    reverse
    > lookup. Try putting the ips in that range either in your reverse NS, or
    > /etc/hosts file.
    >
    >
    > ----- Original Message -----
    > From: "Maikel L. Miranda" <admin@jovenclub.cu>
    > To: <freebsd-isp@freebsd.org>
    > Sent: Saturday, March 20, 2004 12:06 AM
    > Subject: unknow tcp/ip problem
    >
    >
    > Hi:
    >
    > Recently I installed FreeBSD 5.1 (on a P4 Xeon at 2.4GHz 1GB RAM) and it
    > worked fine except for one thing: I can't access to any services of the
    > server (ssh or telnet, this one's just for tests) from one subnet (Remote
    > Access, attached to a Computone RAS 2000). The ping respond ok in both
    > directions, the log of my ssh client gives me this:
    >
    > 2004-03-19 23:41:42 Looking up host "192.168.1.25"
    > 2004-03-19 23:41:42 Connecting to 192.168.1.25 port 22
    > 2004-03-19 23:41:43 Server version: SSH-1.99-OpenSSH_3.6.1p1
    > FreeBSD-20030924
    > 2004-03-19 23:41:43 We claim version: SSH-1.5-PuTTY-Release-0.53b
    > 2004-03-19 23:41:43 Using SSH protocol version 1
    >
    > The telnet just hang out after I type the password. From the rest of the
    > network (500 computers more less) it works exelent. I've gone trough the
    > configuration over and over but I can't find any possible problem. I have
    > others servers (Gigaserver 6000) running FreeBSD 5.1 in the same segment
    of
    > the network and they work OK.
    >
    > Does anyone has had a problem like this?. I will apreciate any help.
    >
    > Thanks,
    > Maikel L. Miranda.
    >
    > _______________________________________________
    > freebsd-isp@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
    >
    >

    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"


  • Next message: Maikel L. Miranda: "Re: unknow tcp/ip problem"

    Relevant Pages

    • Re: reverse DNS resolution...
      ... We're trying to get reverse DNS resolution for a block of IPs ... We've had the 10.x network working great at the office ... your DNS needs to be authoritative for both forward and reverse. ... If you are trying to do this for less then a /24 block the zone files ...
      (freebsd-questions)
    • Re: reverse DNS resolution...
      ... We're trying to get reverse DNS resolution for a block of IPs ... We've had the 10.x network working great at the office ... your DNS needs to be authoritative for both forward and reverse. ... IN PTR user1.vpn. ...
      (freebsd-questions)
    • Re: ssh login issue
      ... Anyone know why this is happening when I remotely ssh in to a 5.3p amd64 ... reverse mapping checking getaddrinfo for athlon failed - POSSIBLE BREAKIN ... People have suggested a mis-configured named setup, ... The local network is small ...
      (comp.unix.bsd.freebsd.misc)
    • Re: Firewall Client Extremely Chatty
      ... a hacker taking control of an internal machine by doing a reverse IP out of ... help its owner characterize all traffic that enters or leaves a network. ... it's often the firewall console that is your first ... Because 95% of all computer infections start from inside the network. ...
      (microsoft.public.isa)
    • Reverse connection on VNC not working on WinXP
      ... I installed on several terminal on a network TightVNC with reverse ... connection. ... this network I have 4 Win98 and 2 WinXP. ...
      (microsoft.public.isa)