Ok, here's a doozie.
I have Windows 2003 Server (shud be similar to W2K Server) running RRAS with NAT turned on.
Demand-dial is on so whenever the remote computers tries to access the net, it automatically dials from the server and and automatically disconnects after 5 minutes of internet inactivity. (note: I've used "remote" to mean computers outside of the server but still part of the LAN network.)
Everything works wonderfully EXCEPT... when they want to FORCE the modem to disconnect, eg by physically turning off the modem, or by unplugging the phone line.
After turning back on the modem (or plugging the phone line back in), the remote computers can't seem to re-activate the demand-dial of RRAS (the modem does not autmoatically dial for the remote users).
Going back into the server and openning up the RRAS management console, I find that the Demand-Dial Interface (in Network Interface) says that the connection is "unreachable". The only way to bring this back up is by Right-Clicking on the Interface and triggering "Connect". From there, when it goes offline again, the remote users can again use the demand-dial interface. Weird.
Anyway, after playing around with settings and trying different things, Im still stuck. Hmmm...
There must be a way to control the Connect and Disconnect part of the Demand-Dial Interface from a command line or remotely.
I found a program called psexec.exe which can run programs remotely. Now I've tried running remotely via
to stop it (instead of turning off the machine) and
to start it again. This time it kind of work, remote computers can invoke the demand-dial but when it dials-out, the connection is not accepted by the ISP server and disconnects (Im not sure why). After this error the the demand-dial interface cannot be invoked by the remote users again.
There must be a way to handle this using a script (or command line) to invoke the Connect and Disconnect part of the Demand-Dial Interface.
Please help... thanks.
ps. Sorry about the long saga.
I have Windows 2003 Server (shud be similar to W2K Server) running RRAS with NAT turned on.
Demand-dial is on so whenever the remote computers tries to access the net, it automatically dials from the server and and automatically disconnects after 5 minutes of internet inactivity. (note: I've used "remote" to mean computers outside of the server but still part of the LAN network.)
Everything works wonderfully EXCEPT... when they want to FORCE the modem to disconnect, eg by physically turning off the modem, or by unplugging the phone line.
After turning back on the modem (or plugging the phone line back in), the remote computers can't seem to re-activate the demand-dial of RRAS (the modem does not autmoatically dial for the remote users).
Going back into the server and openning up the RRAS management console, I find that the Demand-Dial Interface (in Network Interface) says that the connection is "unreachable". The only way to bring this back up is by Right-Clicking on the Interface and triggering "Connect". From there, when it goes offline again, the remote users can again use the demand-dial interface. Weird.
Anyway, after playing around with settings and trying different things, Im still stuck. Hmmm...
There must be a way to control the Connect and Disconnect part of the Demand-Dial Interface from a command line or remotely.
I found a program called psexec.exe which can run programs remotely. Now I've tried running remotely via
Code:
psexec \\<server> net stop remoteaccess
Code:
psexec \\<server> net start remoteaccessThere must be a way to handle this using a script (or command line) to invoke the Connect and Disconnect part of the Demand-Dial Interface.
Please help... thanks.
ps. Sorry about the long saga.
