Can ping one, but not the other (but can ping both from another)
Results 1 to 8 of 8

Thread: Can ping one, but not the other (but can ping both from another)

  1. #1
    Registered User
    Join Date
    Aug 1999
    Location
    near the backdoor to hell
    Posts
    804

    Can ping one, but not the other (but can ping both from another)

    I've got two systems, well actually, about 90 some systems..

    All of which are on a local lan, with no routing or firewalls between them.

    Server "A" (IP:192.168.1.2) can ping 192.168.1.200 just fine (HP Jetdirect in an HP 5) - but can not ping 192.168.1.201 (HP Jetdirect in a HP 4200)

    Server "B" can ping both. (IP:192.168.1.3)

    Both have the same information in the TCP/IP Configuration, other than the IP address, and both are referring to eachother's DNS first (AD Int.), then themselves, then a 3rd internal DNS Server (secondary)

    DNS Names resolve fine to the printer, just that pinging from Server "A" results in timeouts.

    Routing table looks fine, and in fact, the ARP Table on Server "A" shows the IP and MAC for the non-pingable printer.

    Server "B" is running Windows 2000 Server (SP3), SQL 2000, with DNS and WINS.
    Server "A" is running Windows 2000 Server (SP4), Exchange 2000 (SP3(a?)), DNS, WINS, and DHCP.

    There is a routing table on both of these boxes dealing with our WAN, but both servers havce this information...

    Any ideas?

  2. #2
    Chat Operator Matridom's Avatar
    Join Date
    Jan 2002
    Location
    Ontario, Canada
    Posts
    3,778
    subnet masks for both systems?

  3. #3
    Registered User
    Join Date
    Aug 1999
    Location
    near the backdoor to hell
    Posts
    804
    Quote Originally Posted by Matridom
    subnet masks for both systems?

    Same

    I think I'll bounce one of the servers, it has been up for over 1K hours...

  4. #4
    Registered User
    Join Date
    Aug 1999
    Location
    near the backdoor to hell
    Posts
    804
    Quote Originally Posted by kannibul
    Same

    I think I'll bounce one of the servers, it has been up for over 1K hours...

    Still no luck. I even bumped the DHCP Reservation for the printer to another IP (192.168.1.201=>192.168.1.202) address, and I still can't ping it from Server "A"...

  5. #5
    Registered User gazzak's Avatar
    Join Date
    Jun 2002
    Location
    London, England
    Posts
    3,595
    Is this a recent thing or has it always happened? Did you install / change anything just before this started?

  6. #6
    Registered User
    Join Date
    Aug 1999
    Location
    near the backdoor to hell
    Posts
    804
    Quote Originally Posted by gazzak
    Is this a recent thing or has it always happened? Did you install / change anything just before this started?
    Nothing in regards to networking. Even so, it's been several months since my last round of service-packing and hotfixes.

    I think I won;t worry about it - before July, we intend to go to W2K3 + EX2K3, plus a new server system (about 8.5K - WSCA Pricing (means about 12K for corporates!))

  7. #7
    Registered User gazzak's Avatar
    Join Date
    Jun 2002
    Location
    London, England
    Posts
    3,595
    Quote Originally Posted by kannibul
    Nothing in regards to networking. Even so, it's been several months since my last round of service-packing and hotfixes.

    I think I won;t worry about it - before July, we intend to go to W2K3 + EX2K3, plus a new server system (about 8.5K - WSCA Pricing (means about 12K for corporates!))
    I'll drink to that. If it aint broke, don't fix it

  8. #8
    Registered User Green_Eyed's Avatar
    Join Date
    Feb 2001
    Location
    Just this side of normal
    Posts
    189
    OK, so you can't ping. The real question is, can you print?

    Like he said, if it aint broke, don't fix it. I would be more concerned if it was printing.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •