S
Simon Bleif
Hi,
I experience the following strange behavior:
I have a server running Windows Server 2003 and a DSL-Modem attached to a
NIC. So I created a new RRAS interface (static) using the built-in PPOE
driver and had no problems so far.
But now, when I wanted to connect/disconnect that interface using netsh
(it worked just fine when I did that by using the RRAS snap-in), I
experienced the following:
netsh
netsh>interface
netsh interface>show interface
Admin State State Type Interface Name
--------------------------------------------------------------
Enabled Connected Loopback Loopback
Enabled Connected Internal Internal
Enabled Connected Dedicated LAN
Enabled Disconnected Full Router DSL
Enabled Connected Full Router intra.net
netsh interface>set interface dsl enabled connect
An interface with this name is not registered with the router.
I thought this problem might have occured because the interface was
configured as static interface, so i switched the interface mode to
demand-dial, rebooted the server and experienced exactly the same
behavior.
I have installed all the updates, patches and fixes available from
Windows Update.
Help would be greatly appreciated.
Simon
I experience the following strange behavior:
I have a server running Windows Server 2003 and a DSL-Modem attached to a
NIC. So I created a new RRAS interface (static) using the built-in PPOE
driver and had no problems so far.
But now, when I wanted to connect/disconnect that interface using netsh
(it worked just fine when I did that by using the RRAS snap-in), I
experienced the following:
netsh
netsh>interface
netsh interface>show interface
Admin State State Type Interface Name
--------------------------------------------------------------
Enabled Connected Loopback Loopback
Enabled Connected Internal Internal
Enabled Connected Dedicated LAN
Enabled Disconnected Full Router DSL
Enabled Connected Full Router intra.net
netsh interface>set interface dsl enabled connect
An interface with this name is not registered with the router.
I thought this problem might have occured because the interface was
configured as static interface, so i switched the interface mode to
demand-dial, rebooted the server and experienced exactly the same
behavior.
I have installed all the updates, patches and fixes available from
Windows Update.
Help would be greatly appreciated.
Simon