FreePPP,TCP/IP multiple configs + ISP's conflicts
Posted on 1997-07-18
subject: TCP/IP multiple config. / ISP log on conflicts
If anybody could give some expert advice (God knows, my ISP doesn't have a clue!) on this problem I would greatly appreciate it.
The run down:
I am using: OT 1.1.2
I have 2 ISP's, 1 uses a PPP server/connection (univ. account) and the other uses a BootP server/connection (AOL).
I frequently go between the 2 in a given session. I have no problem switching the TCP/IP control panel configs (I actually have the configs saved so I can minimize my clicking). I also have several third party items to assist in the hassle of switching ( control strips, control panels, extension), but that's not the real problem.
The REAL problem:
When I first connect to my PPP server/account, use it, quit; then switch the TCP/IP config - everything seems fine. I then log on to the BootP server(AOL) and it works fine EXCEPT, I can't run Netscape. I get the message that 'Netscape was unable to open a network socket connection
REAL Problem #2
If I start out with my AOL (TCP/IP configured before start-up) account(BootP server) and activate Netscape - it works fine; but if I try to go back to my PPP server/account and then run Telnet 2.7, I get an error code 11
My insight: I think the TCP/IP driver is not allowing the config to be totally recognized in some way or another to differing servers in the same session, or the config is not totally recognized so that adjunct software can be utilized through a given Internet connection (i.e. AOL connection)
I was told that I would have to restart my computer with the new TCP/IP config everytime I want to use a different ISP. Surely this is not true, is it??????
That defeats the purpose/need for having different ISP's. There surely must be a way of switch the connection configs, w/o restarting, on-the-fly and during the same session - but, in a way that will allow me to run whatever software without weirdo error messages and crashes.
I truly believe the problem lies in the TCP/IP driver. Perhaps it has its limitations and this is one of them.
Further thought leads me to believe that the serial/modem port is not relinquishing the code info sent by the TCP/IP driver or OT, thus not allowing a completely compatible connection for whatever server I am currently on,
Ohh, BTW, before someone suggests reinstalls, I've reinstalled pertinent items about 5X in the past 2 days - same problems occur.
HELP!!!! is greatly appreciated