Cannot Connect to Internet and MSN or other Dialup with Two Network Cards -SOLUTION

Problem:

I want to have TCP/IP to my cable modem, TCP/IP to my local lan (on a separate ethernet card, for security reasons) and TCP/IP with dial-up networking (because my Wave service is still flakey -grrr :)

Win95 won't add any routes to a third interface in the routing table, so I have to remove tcp/ip from one of my ethernet cards, reboot and then dial in.

Here's what Microsoft says about it. It's good for a sad laugh anyway.

http://www.microsoft.com/kb/articles/q140/4/60.htm

...and here's another article about the problem:

http://www.microsoft.com/kb/articles/q142/7/33.htm

The TechNet article was posted late '96.

Answer 1:

A solution is (well, maybe) to use Trumpet Winsock for Win95.

It's available at: http://www.trumpet.com.au

M$ are really low for not suggesting this in their KB article but what else would you expect from them?

It does not seem to use the route table and I'm not sure how to determine which packets will go thru trumpet and which will go thru your local lan... You have to spend some time learning how to use it. It will take a bit of experimentation so it doesn't c rash. It does what I need to do and that's what counts.

Answer 2:

In addition to trumpet as a solution, I know that Win97 Memphis Beta has fixed the problem. You can have at least 2 ethernet TCP/IP and one SLIP/PPP Dialup TCP/IP.

Perhaps this would apply to OSR-2 as well?

Search Terms:

Article ID: Q142733 The information in this article applies to: The Microsoft Network versions 1.05, 1.2, 1.3, 2.0 ARTICLE-ID: Q140460 TITLE : Dial-Up Networking Does Not Obtain an IP Address KBCategory: kbenv KBSubcategory: msnconnect msninternet Additional reference words: 1.20 1.30 2.00 msn dual homing KBCategory: kbnetwork kbenv kbpolicy KBSubcategory: win95 dun Additional reference words: 95

Created Sunday, Feb. 09, 1997

http://www.Seanster.com/cable/Multihoming.html

//End of File