🚀 go-pugleaf

You probably have the Internet setting "Connect to internet as needed".  I
have the same set up and turned this option off.  Whenever I pinged or
telneted I would get the Dial up network window.  But I now have to start
up Dialup network manually when ever I cruise...

Phil Chapman <phil@scwi.com> wrote in article
<5se1au$grp$1@viper.america.net>...
>  I have a system that runs TCPIP on both the dial-up adapter,  which is
used
> for the internet.  And another TCPIP running on a LAN.
> 
> It shows up as being separate in the TCPIP configuration.  But when you
try
> to run the LAN TCPIP it pulls up the dial-up adapter.
> 
> Please HELP!
> 
> 
> --
> Phil Chapman
> phil@scwi.com
> http://www.scwi.com
> 
> 
> 
> 

"Phil Chapman" <phil@scwi.com> wrote:

> I have a system that runs TCPIP on both the dial-up adapter,  which is used
>for the internet.  And another TCPIP running on a LAN.
>
>It shows up as being separate in the TCPIP configuration.  But when you try
>to run the LAN TCPIP it pulls up the dial-up adapter.

I'll venture a guess that you have multiple IP networks on your LAN.
I'll venture even further to guess that you're using Microsoft's
TCP/IP stack for Win95.  I assume these because TCP/IP stacks
(usually) use interface IP addresses to determine which interface to
use.  Microsoft's TCP/IP stack also is terrible at handling multiple
interfaces.

For example, say you have a serial interface 205.230.172.5 and a LAN
interface 172.16.121.12.  You try to connect to a device 172.16.112.5.
Because this device's IP network address (172.16, Class B) matches
that of your LAN interface, TCP/IP uses your LAN interface to send the
packet. 

Next, you try to connect to a device 198.172.16.3.  Because this
device's IP network address (198.172.16, Class C) doesn't match the IP
network address for either of your interfaces, your TCP/IP stack makes
an "educated guess" and defaults to using your primary interface.

For some unknown reason, Microsoft's TCP/IP stack typically defaults
to using the Dial-Up Adapter as the default TCP/IP interface.  Great
for Internet connections but terrible for LAN TCP/IP.

How to fix, hmmmmm.... well, the ideal fix would be to let the LAN
deal with it.  Get the serial interface out of your system and add a
router to your network to handle Internet IP, say for example a Cisco
or Bay Networks router.  Get the administrator (if not yourself) to
configure the router's IP tables to ignore any in-house traffic &
route the rest.  Of course, this calls for a dedicated line, firewalls
and not a little $$$$$.  For cheaper LAN-type solutions you might want
to look at a package called WinGate.  I've never worked with it
myself, but a "reliable" source tells me that it does basically the
same thing as a hardware router.  Then there's Internet-in-a-box,
Internet-Gateway and a whole slew of others.

Next-best (or if you *really* want to keep the modem in your PC) would
be to set up static routes for all of your LAN's IP networks.  If
traffic wasn't local to either of the interfaces then the TCP/IP stack
would look in the static route table to figure out which interface to
use (in our case the LAN interface, limited networks).  If it didn't
find a match it would default to using the primary interface (in our
case the Dial-Up Adapter, unlimited network).  Unfortunately,
Microsoft's TCP/IP stack doesn't support static routes.  A pity.  Most
other stacks do.  

If you're interested in trying different stacks, take a look at
NetManage's Chameleon or WRQ's Reflection.  Both very nice packages
with lots of functionality.

Hope this helps...


     Wallace Marks          ("`''-/").___..--''"`-._
  Systems Administrator      `6_ 6  )   `-.   (    ).`-.__.`)
National Vision Associates   (_Y_.)'  ._   )  `._ `. ``-..-'
(770) 822-2030 / 2381 Fax  _..`--'_..-_/  /--'_.' ,'
   wmarks@atlcom.net      (il),-''  (li),'  ((!.-'

Now with all of that being said, try this.

0. (ooops forgot this one) First check with the Network Admin to make sure
you can do this. :-)
1. Select network properties from control panel.
2. Select the TCP/IP protocol from the list and modify its properties.
3. Under the DNS tab, ADD the IP address of your LAN server.
4. "OK" your way out, and reboot the computer, this should help.


wmarks@atlcom.net (Wallace Marks) wrote in article
<A339DC6C456B8503.0B39DD7CEC254BD2.344C58C7B9F6E5E2@library-proxy.airnews.ne
t>...
> "Phil Chapman" <phil@scwi.com> wrote:
> 
> > I have a system that runs TCPIP on both the dial-up adapter,  which is
used
> >for the internet.  And another TCPIP running on a LAN.
> >
> >It shows up as being separate in the TCPIP configuration.  But when you
try
> >to run the LAN TCPIP it pulls up the dial-up adapter.
> 
> I'll venture a guess that you have multiple IP networks on your LAN.
> I'll venture even further to guess that you're using Microsoft's
> TCP/IP stack for Win95.  I assume these because TCP/IP stacks
> (usually) use interface IP addresses to determine which interface to
> use.  Microsoft's TCP/IP stack also is terrible at handling multiple
> interfaces.
> 
> For example, say you have a serial interface 205.230.172.5 and a LAN
> interface 172.16.121.12.  You try to connect to a device 172.16.112.5.
> Because this device's IP network address (172.16, Class B) matches
> that of your LAN interface, TCP/IP uses your LAN interface to send the
> packet. 
> 
> Next, you try to connect to a device 198.172.16.3.  Because this
> device's IP network address (198.172.16, Class C) doesn't match the IP
> network address for either of your interfaces, your TCP/IP stack makes
> an "educated guess" and defaults to using your primary interface.
> 
> For some unknown reason, Microsoft's TCP/IP stack typically defaults
> to using the Dial-Up Adapter as the default TCP/IP interface.  Great
> for Internet connections but terrible for LAN TCP/IP.
> 
> How to fix, hmmmmm.... well, the ideal fix would be to let the LAN
> deal with it.  Get the serial interface out of your system and add a
> router to your network to handle Internet IP, say for example a Cisco
> or Bay Networks router.  Get the administrator (if not yourself) to
> configure the router's IP tables to ignore any in-house traffic &
> route the rest.  Of course, this calls for a dedicated line, firewalls
> and not a little $$$$$.  For cheaper LAN-type solutions you might want
> to look at a package called WinGate.  I've never worked with it
> myself, but a "reliable" source tells me that it does basically the
> same thing as a hardware router.  Then there's Internet-in-a-box,
> Internet-Gateway and a whole slew of others.
> 
> Next-best (or if you *really* want to keep the modem in your PC) would
> be to set up static routes for all of your LAN's IP networks.  If
> traffic wasn't local to either of the interfaces then the TCP/IP stack
> would look in the static route table to figure out which interface to
> use (in our case the LAN interface, limited networks).  If it didn't
> find a match it would default to using the primary interface (in our
> case the Dial-Up Adapter, unlimited network).  Unfortunately,
> Microsoft's TCP/IP stack doesn't support static routes.  A pity.  Most
> other stacks do.  
> 
> If you're interested in trying different stacks, take a look at
> NetManage's Chameleon or WRQ's Reflection.  Both very nice packages
> with lots of functionality.
> 
> Hope this helps...
> 
> 
>      Wallace Marks          ("`''-/").___..--''"`-._
>   Systems Administrator      `6_ 6  )   `-.   (    ).`-.__.`)
> National Vision Associates   (_Y_.)'  ._   )  `._ `. ``-..-'
> (770) 822-2030 / 2381 Fax  _..`--'_..-_/  /--'_.' ,'
>    wmarks@atlcom.net      (il),-''  (li),'  ((!.-'
> 
> 
>