× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: TCP/IP problem
  • From: Larry Bolhuis <lbolhui@xxxxxxx>
  • Date: Wed, 14 Oct 1998 22:20:30 -0400
  • Organization: Arbor Solutions, Inc

Art,

   While I have not used the internal NT server yet (ours just arrived)
I do see a problem with the chosen IP Addresses.  Here's the problem:
Your Ethernet and TokenRing networks are on the same TCP/IP Subnet. This
means that the AS/400 must pick one when attempting to communicate to
your PC (Also on the same subnet). It is probably picking incorrectly. 
Try changing the TokenRing interface to 192.168.3.3.  This will put the
NT Ring into another Subnet. You will have to change the IP address for
the NT server itself to a 198.168.3.x address as well in order to get to
it.
   The rule that is any time there is a router between two network
pieces the pieces need to be on different TCP/IP Subnets.  In this case
the AS/400 is the router(or can be), and at the very least is ON two
different networks.

  Larry Bolhuis
  Arbor Solutions, Inc
  lbolhui@ibm.net

Art Tostaine, Jr. wrote:
> 
>  My desktop PC is running NT workstation 4.0.  I want to print
>  using an LPD
>  client to my PC (Client Access gives GPF when using TCP/IP printing)
> 
>  My TCP config on AS/400 looks like this:
> 
>                            Work with TCP/IP Interfaces
> 
>        Internet         Subnet              Line      Line
>   Opt  Address          Mask             Description  Type
> 
>        127.0.0.1        255.0.0.0        *LOOPBACK    *NONE
>        192.168.2.2      255.255.255.0    ETHERNET     *ELAN
>        192.168.2.3      255.255.255.0    CCANT00      *TRLAN
> 
>  The *TRLAN I guess is the internal *LAN adapter that
>  communicates with NT
>  Server running on IPCS.
> 
>  My PC is 192.168.2.15
> 
>  AS/400 can't print to my PC unless I end the 192.168.2.3
>  interface.  I use
>  Client Access PC5250 to access 400 normally.  But I can't
>  print (or ping)
>  unless I end the *TRLAN.
> 
>  I assume that I have some kind of problem with my chosen TCP
>  addresses?
> 
>  Art Tostaine, Jr.
>  CCA, Inc.
>  Parlin, NJ  08859
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.