RE: Ping and general network weirdness

From: John Brooks (john_at_day-light.com)
Date: 06/30/05

  • Next message: Galdes, Andrew (ERHS): "FreeBSD 5.4 and NFS"
    To: "Phil Cooper" <sendphilmail@gmail.com>, <freebsd-questions@freebsd.org>
    Date: Wed, 29 Jun 2005 19:27:46 -0500
    
    

    run:

      dig fragile.mshome.net a
      more /etc/resolv.conf
      more /etc/host.conf
      more /etc/hosts

    that should give you some good clues

    --
    John Brooks
    john@day-light.com 
    > -----Original Message-----
    > From: owner-freebsd-questions@freebsd.org
    > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Phil Cooper
    > Sent: Wednesday, June 29, 2005 7:10 PM
    > To: freebsd-questions@freebsd.org
    > Subject: Re: Ping and general network weirdness
    > 
    > 
    > Thanks;
    > 
    > I checked with ifconfig, and fragile's IP is actually 192.168.0.224,  
    > and I put this in the hosts file.
    > 
    > Now, I can ping and ssh into fragile using the IP address, but  
    > pinging "fragile" still assumes 192.168.0.116 is it's IP - so does  
    > the fault now lie with the other machines on the network? How do I  
    > get them to realise that fragile==192.168.0.224 and not .116?
    > 
    > - P
    > 
    > 
    > On 30 Jun 2005, at 00:57, fbsd_user wrote:
    > >
    > > Do you have fragile.mshome.net in the /etc/hosts  file?
    > >
    > > To ping using fragile.mshome.net you would need a DSN server
    > > to resolve that name to an internal IP address.
    > >
    > > Look in the ports collection for djbdns
    > >
    > >
    > > -----Original Message-----
    > > From: owner-freebsd-questions@freebsd.org
    > > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Phil Cooper
    > > Sent: Wednesday, June 29, 2005 7:43 PM
    > > To: freebsd-questions@freebsd.org
    > > Subject: Ping and general network weirdness
    > >
    > >
    > > Hi everybody;
    > >
    > > Not doing too well with my first freeBSD install. I have a machine
    > > set up with the name "fragile", no ipv6, DHCP, no ipfw, and sshd on.
    > >
    > > Problem is, I can ping out to other machines on the network, or to
    > > another machine on the Internet ('net connection via another winXP
    > > machine), but neither of the other machine on the network can ping
    > > fragile. Fragile can ping itself via localhost, but not by name.
    > >
    > >  From any machine, or fragile itself, pinging "fragile" or the IP
    > > gives:
    > >
    > > bramley:~ phil$ ping fragile
    > > PING fragile.mshome.net (192.168.0.116): 56 data bytes
    > > ping: sendto: No route to host
    > > ping: sendto: Host is down
    > > ping: sendto: Host is down
    > > ping: sendto: Host is down
    > > ping: sendto: Host is down
    > > ^C
    > > --- fragile.mshome.net ping statistics ---
    > > 10 packets transmitted, 0 packets received, 100% packet loss
    > > bramley:~ phil$
    > >
    > > Any ideas?
    > >
    > >
    > >
    > >
    > > _______________________________________________
    > > freebsd-questions@freebsd.org mailing list
    > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > > To unsubscribe, send any mail to
    > > "freebsd-questions-unsubscribe@freebsd.org"
    > >
    > >
    > 
    > 
    > 
    > _______________________________________________
    > freebsd-questions@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > To unsubscribe, send any mail to 
    > "freebsd-questions-unsubscribe@freebsd.org"
    > 
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Galdes, Andrew (ERHS): "FreeBSD 5.4 and NFS"

    Relevant Pages

    • Re: One computer cant see the other.
      ... I'm not sure I'm doing this right Steve, but on the command prompt at my host ... command prompt on my host machine and my client machine when I ping the host. ... network of two computers. ... The most likely problem is that a firewall (Norton, McAfee, ZoneAlarm, ...
      (microsoft.public.windowsxp.network_web)
    • Re: simple networking question
      ... Can the hardware PC's ping each other? ... company so why can't I network two pcs together?? ... I'm guessing you can ping by IP but not host name. ... virtualization). ...
      (microsoft.public.windows.server.general)
    • Re: Web Site Mystery
      ... there is a pointer to the ip address of the host ... When I ping any other address it does resolve to an ip address but returns ... www.europacrown.com don't work from our corporate network. ... promoted our a SQL server to act as a domain controller and active ...
      (microsoft.public.windows.server.general)
    • Re: Mshome is not accessible
      ... Windows Network, and select the workgroup I get: ... Mshome is not accessible. ... All computers are running Windows XP SP2 and are members of the MSHOME ... Computer A can ping using ping hom100fr001. ...
      (microsoft.public.windowsxp.network_web)
    • Re: DHCP and DNS
      ... Assuming you can ping the computer by IP, can you ping it by FQDN? ... I have about 120 Win XP Pro users on my network, ... About 10% of the users cannot resolve the new host name. ... I can make name resolution work by changing the IP configuration from ...
      (microsoft.public.windowsxp.network_web)