public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: Newbie <linux-newbie@vger.kernel.org>
Subject: Re: Fwd: W$ 2K...
Date: Mon, 28 Jul 2003 12:15:54 -0700	[thread overview]
Message-ID: <5.1.0.14.1.20030728115610.01ee9cd8@celine> (raw)
In-Reply-To: <200307282028.39516.James.Hatridge@epost.de>

At 08:28 PM 7/28/2003 +0200, James Hatridge wrote:
[...]
> > >But when I ping from Opus to
> > >Penguin, Opus gets nothing, but Penguin give an error.
> >
> > What is the error (the actual message, word for word) and where goes
>
>I don't have the system up at the moment, but the W$ error was something 
>about
>an IP and not allowed etc.
>
> > Penguin "give" it?

First, you only answered half the question. Since this is an attempt to 
ping the Win2K host from the Linux host, there is no *obvious* place for 
the Win2K machine to display an error message. So, once gain, please 
mention *where* "Penguin gives an error" (since, in part of the message 
omitted here, you say Penguin is the Win2K host).

Second, as you surely knew without my saying, "something about an IP and 
not allowed etc." is not much as error reports go. It does make me wonder 
if you have some firewalling installed in the Win2K system that blocks 
Opus's IP address. But that is fishing wildly.

So when you have the Win2K system up, try again and post exact answers to 
the "what" and "where" of this error message. Since (you say) Penguin *can* 
ping Opus successfully, basic connectivity is OK, so we need to look for a 
more subtle problem.

Also, provide the networking basics:

         from Opus, output of "ifconfig" (or "ip -s link show") and 
"netstat -nr"
         from Penguin, output (in a DOS box) of "ipconfig" and "route print"

Now, the usual way to specify networking information on Win2K hosts in in
         Start->Settings->Control Panel->Network and Dial-Up->
                 Local Area Connection->Properties->
                 Internet Protocol (TCP/IP)->Properties

If you did not do it that way, tell us how you did it. In either case, did 
you assign an address and related info statically, or did you tell the 
system to use a DHCP server (if you have one on your LAN)? Same questions 
for DNS.

Finally, since you also tell us that there are "5 other Linux systems up 
and running on
this net and one DOS system" ... do pings from these other hosts to the 
WIn2K machine generate the same error message?



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2003-07-28 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28  4:41 Fwd: W$ 2K James Hatridge
2003-07-28 11:37 ` Frank Roberts - SOTL
2003-07-28 13:58 ` Ray Olszewski
2003-07-28 18:28   ` James Hatridge
2003-07-28 19:15     ` Ray Olszewski [this message]
2003-07-28 19:20       ` Dan Zlotnikov
2003-07-30 15:01       ` James Hatridge
2003-07-30 18:26         ` James Ferris
2003-07-31 13:17           ` James Hatridge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20030728115610.01ee9cd8@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox