Still getting Internet Explorer error message before Barricade router completes dial-up connection

[Karl Loucks]

Still having this problem. I installed one Windows XP PC and upgraded
the ME machine to XP Pro because the older operating systems are
getting obsolete. On the Windows XP PC's, I tried increasing the
NameSvrQueryTimeout setting to 120000, but the problem persists as
before (stated below). I also tried to do what Brian Smither had
suggested in his post, but I don't have the registry keys he
mentioned.

Looking at my setup, it is similiar to a Windows ICS setup, except the
host is not a Windows PC with ICS, but the Barricade router. Keeping
this in mind, could I set up the XP PC's as ICS client machines,
keeping the router as the "host" (i.e. the piece of hardware which is
actually connecting to the internet)?

Or is there another way to set up the PC's so they see the router as
the host and themselves as clients?

Description of problem:
When I access a Web page such as www.cnn.com, the Barricade router
causes the attached dial-up modem to dial, but the Internet Explorer
gives a message stating it cannot access the site requested. When I
try to access the same site again, the site will come up. It is a
Barricade 7004ABR router with a US Robotics model 5686 external 56K
modem. This happens on 2 PC's on the network, which is a peer-to-peer
setup. There are 5 PC's on the LAN, I do not have the
others set up to use the Barricade yet. How can I get the browser to
access the sites the first time?

TIA,
Karl

 

[Chris]

It sounds like the router is still dialing up and logging
in when you first attempt to access a webpage. Why not
put a ping command in the startup of all machines that
pings www.cnn.com to establish the connection before the
user has a chance to open a browser window? And, most
routers have an option to keep the connection alive for a
specified time after the last connection request.
Increase that value.

 

[Terry]

Still having this problem. I installed one Windows XP PC and upgraded
the ME machine to XP Pro because the older operating systems are
getting obsolete. On the Windows XP PC's, I tried increasing the
NameSvrQueryTimeout setting to 120000, but the problem persists as
before (stated below). I also tried to do what Brian Smither had
suggested in his post, but I don't have the registry keys he
mentioned.

Looking at my setup, it is similiar to a Windows ICS setup, except the
host is not a Windows PC with ICS, but the Barricade router. Keeping
this in mind, could I set up the XP PC's as ICS client machines,
keeping the router as the "host" (i.e. the piece of hardware which is
actually connecting to the internet)?

Or is there another way to set up the PC's so they see the router as
the host and themselves as clients?

Set the gateway as the ip address of the router.