|
Sorry that this is a little OT. I could
do
with some help.
I have a BT Speedway ISDN PCI card (aka AVM
Fritz
card) in my Windows 2000 server. I connect to BT Internet Anytime
using it
(NDISWAN connection). The connection is brought up / down by "Dialer
2000"
which I know some of you use (basically is built on top of the normal MS
DUN
client, but allows for 'redials' automatically / at timed
intervals).
When I first connect, things work fine and
running
IPCONFIG gives the following results:
D:\>ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area
Connection:
Connection-specific DNS Suffix .
:
IP Address. . . . . . . . .
. .
. : 192.168.0.1
Subnet Mask .
. .
. . . . . . . . :
255.255.255.0
Default Gateway . . . . . . . . . :
PPP adapter BT Internet 0800:
Connection-specific DNS Suffix .
:
IP Address. . . . . . . . .
. .
. : 213.122.79.30
Subnet Mask
. .
. . . . . . . . . :
255.255.255.255
Default
Gateway .
. . . . . . . . : 213.122.79.30
========================
But if I disconnect / reconnect I get the
following:
D:\>ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area
Connection:
Connection-specific DNS Suffix .
:
IP Address. . . . . . . . .
. .
. : 192.168.0.1
Subnet Mask .
. .
. . . . . . . . :
255.255.255.0
Default Gateway . . . . . . . . . :
PPP adapter BT Internet 0800:
Connection-specific DNS Suffix .
:
IP Address. . . . . . . . .
. .
. : 0.0.0.0
Subnet Mask . . .
. .
. . . . . . : 0.0.0.0
Default
Gateway . . . . . . . . . :
PPP adapter ?:
Connection-specific DNS Suffix .
:
IP Address. . . . . . . . .
. .
. : 213.122.172.129
Subnet
Mask .
. . . . . . . . . . :
255.255.255.255
Default
Gateway .
. . . . . . . . : 213.122.172.129
========================
As the server is up & running, it makes / drops the connection
during
the day and I get more & more of these PPP adapters appearing.
The
problem is that my Internet Connection Sharing software does not appear to
work
properly after this second PPP adapter appears.
If I reboot the PC, everything starts working as it should.
My thoughts were that the driver for the ISDN card is the source of
the
problems, but the tech support team for the card say the problem is nothing
to
do with their s/w.
Thoughts / suggestions would be most
welcome.
| Yahoo! Groups
Sponsor |
;) |
|
For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe: ukha_d-subscribe@xxxxxxx
Unsubscribe: ukha_d-unsubscribe@xxxxxxx
List owner: ukha_d-owner@xxxxxxx
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|