XP TCP/IP Connections Madness

[clevelandtexas]

I use Roadrunner via a cable modem. I also have a 56k dial-up modem. I use Roadrunner for all my internet stuff. I use my 56k modem to dial into work. MS, in all their wisdom, has made it impossible for me to be dialed into work though my 56k modem (using PC Anywhere) and have internet access through my cable modem. The 56k modem connections dominate. It seems that I can't have two MSIE browser sessions where one would use Roadrunner the the other my 56k modem.

Is there any good solution to this? Can I split these apart by using Netscape's browser for Roadrunner and MSIE for my 56k modem?

:rolleyes:

[BDillon21]

I don't know if I can be of much help, but are you using RAS to dial in to a RAS server, then using pcAnywhere over TCP/IP? If so, tell your RAS connection to NOT use the default gateway on remote network. I have Internet access at work via a T1 line, I use pcAnywhere over 56k modem to connect to satellite offices with no problem at all with Win XP pro.

If you are using RAS then its connection will override your local LAN settings. You have the ability to disable using the default gateway but I'm not sure if you can bind more than one IP to a NIC with Win XP like you can with Win2k Server.

Edit:

I fogot to mention that I am also using pcAnywhere Version 10.5. It also worked for me with version 10.0

[clevelandtexas]

I have the exact problem you describe. However if I disable the default gateway I can dial in but PC Anywhere just won't connect. Didn't have the problem with Win98. Thank you Mr. Gates for your Win XP 'improvements'. :)

[BDillon21]

OK, here are my thoughts. IF you are dialing in to a RAS server, and then trying to use pcAnywhere to get around, and unchecking the use default gateway on remote network causes pcAnywhere not to connect, then the PC you are trying to connect to is on a different subnet. In which case if you disable the default gateway then you would not be able to browse any other computers on the other side of your router. In which case I don't think any OS would be able to work around that, its just how TCP/IP works. Are you dialing in to a large corporate network?

Also, if U could probably help more if you were able to give me more specifics about exactly how you are trying to connect and what exactly you are trying to connect to. Perhaps a little about the topology of your corporate network if you know it.

Also, make sure that your LAN connections are listed first in your bindings. DNS accesses these in the order they are listed, so if RAS is first and it finds what it needs, then it has no need to go anywhere else to look for it. To view your bindings, right click my network places, properties, advanced, advanced settings.

If this doesn't work then I would have to say your PC is on the other side of a router.