WAN Miniport/ DSL

  • Thread starter Thread starter Tom
  • Start date Start date
T

Tom

I hope someone here can help me... I have had SBC DSL for
about 3 years now. It has always worked well on Win ME.
I recently had to upgrade several parts on my computer,
including the motherboard, processor, hard drive, etc. I
upgraded to Win XP at the same time.

Previously, under ME, there was a set of SBC DSL drivers
that I used to connect. Those refused to work in XP,
though. With telephone assistance from SBC, I was able
to set up my connection using Windows Network Connection
Manager, and it works, but it is a much slower connection
that it used to be. In fact, it is no faster than dial-
up, and online games refuse to connect anymore, lagging
out almost immediately.

The SBC tech support had no solution. I tried a 3rd
party "Internet Speed Booster" program, but saw no
improvement. I ran a testing utility and it gave the
following info:

Network Adapters FAILED
+ [00000001] Intel(R) PRO/100+ Management Adapter with
Alert On LAN* (PASSED)
Caption = [00000001] Intel(R) PRO/100+ Management
Adapter with Alert On LAN*
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultTTL = 0
Description = Intel(R) PRO/100+ Management Adapter with
Alert On LAN* - Packet Scheduler Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 8:14:07 PM 1/18/2038
DHCPLeaseObtained = 11:19:05 AM 9/10/2003
DHCPServer = 255.255.255.255(Invalid IP Address)
DNSEnabledForWINSResolution = FALSE
DNSHostName = samurai
Index = 1
+ IPAddress = 169.254.59.182 (PASSED)
Pinging 169.254.59.182 with 32 bytes of data:
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Ping statistics for 169.254.59.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 30
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.0.0
IPXEnabled = FALSE
KeepAliveTime = 0
MACAddress = 00:90:27:C5:BE:12
PMTUBHDetectEnabled = FALSE
PMTUDiscoveryEnabled = FALSE
ServiceName = E100B
SettingID = {8A81F08B-D3D2-43AA-A4CD-0E259A5CC901}
TcpipNetbiosOptions = 0
TcpWindowSize = 0
WINSEnableLMHostsLookup = TRUE
- [00655363] WAN Miniport (IP) (FAILED)
Caption = [00655363] WAN Miniport (IP)
DatabasePath = %SystemRoot%\System32\drivers\etc
+ DefaultIPGateway = 63.206.88.122(Same Subnet) (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
DefaultTTL = 0
Description = WAN (PPP/SLIP) Interface
DHCPEnabled = FALSE
DNSEnabledForWINSResolution = FALSE
DNSHostName = samurai
- DNSServerSearchOrder (FAILED)
+ 206.13.28.12 (FAILED)
Pinging 206.13.28.12 with 32 bytes of data:
Reply from 206.13.28.12: bytes=32 time=1722ms TTL=1722
Request timed out.
Reply from 206.13.28.12: bytes=32 time=1515ms TTL=1515
Reply from 206.13.28.12: bytes=32 time=1398ms TTL=1398
Ping statistics for 206.13.28.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 1398ms, Maximum = 1722ms, Average = 1545ms
+ 206.13.29.12 (FAILED)
Pinging 206.13.29.12 with 32 bytes of data:
Reply from 206.13.29.12: bytes=32 time=1625ms TTL=1625
Request timed out.
Reply from 206.13.29.12: bytes=32 time=1533ms TTL=1533
Reply from 206.13.29.12: bytes=32 time=1478ms TTL=1478
Ping statistics for 206.13.29.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 1478ms, Maximum = 1625ms, Average = 1545ms
GatewayCostMetric = 1
Index = 655363
+ IPAddress = 63.206.88.122 (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 50
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSubnet = 255.255.255.255
IPXEnabled = FALSE
KeepAliveTime = 0
MACAddress = 00:53:45:00:00:00
PMTUBHDetectEnabled = FALSE
PMTUDiscoveryEnabled = FALSE
ServiceName = NdisWan
TcpipNetbiosOptions = 2
TcpWindowSize = 0
WINSEnableLMHostsLookup = TRUE
- DNS Servers FAILED
- [00655363] WAN Miniport (IP) (FAILED)
- DNSServerSearchOrder (FAILED)
+ 206.13.28.12 (FAILED)
Pinging 206.13.28.12 with 32 bytes of data:
Reply from 206.13.28.12: bytes=32 time=671ms TTL=671
Request timed out.
Request timed out.
Reply from 206.13.28.12: bytes=32 time=1530ms TTL=1530
Ping statistics for 206.13.28.12:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
Approximate round trip times in milli-seconds:
Minimum = 671ms, Maximum = 1530ms, Average = 1100ms
+ 206.13.29.12 (FAILED)
Pinging 206.13.29.12 with 32 bytes of data:
Request timed out.
Reply from 206.13.29.12: bytes=32 time=1530ms TTL=1530
Reply from 206.13.29.12: bytes=32 time=1456ms TTL=1456
Reply from 206.13.29.12: bytes=32 time=1565ms TTL=1565
Ping statistics for 206.13.29.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 1456ms, Maximum = 1565ms, Average = 1517ms
+ Default Gateways PASSED
+ [00655363] WAN Miniport (IP) (PASSED)
+ DefaultIPGateway = 63.206.88.122(Same Subnet) (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
+ DHCP Servers
+ [00000001] Intel(R) PRO/100+ Management Adapter with
Alert On LAN*
DHCPServer = 255.255.255.255(Invalid IP Address)
+ IP Address PASSED
+ [00000001] Intel(R) PRO/100+ Management Adapter with
Alert On LAN* (PASSED)
+ IPAddress = 169.254.59.182 (PASSED)
Pinging 169.254.59.182 with 32 bytes of data:
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Ping statistics for 169.254.59.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
+ [00655363] WAN Miniport (IP) (PASSED)
+ IPAddress = 63.206.88.122 (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
+ Network Clients


Any help or advice would be appreciated. Oh, both the
Ethernet card and DSL modem are nearly 4 years old now...
could it be a hardware problem? And do you find that
Cable or DSL works better with XP?
 
R.click my computer,properties,device mgr.,under network
adapters,R.click the hardware,uninstall,close out,and
reboot,also delete the third party software.
On reboot,desktop,open control-panel,internet connections
R.click the icon,properties,in the L.sub-menu,select,
repair this connection,close out,open windows update.
Update will install drivers for the dsl if available.
-----Original Message-----
I hope someone here can help me... I have had SBC DSL for
about 3 years now. It has always worked well on Win ME.
I recently had to upgrade several parts on my computer,
including the motherboard, processor, hard drive, etc. I
upgraded to Win XP at the same time.

Previously, under ME, there was a set of SBC DSL drivers
that I used to connect. Those refused to work in XP,
though. With telephone assistance from SBC, I was able
to set up my connection using Windows Network Connection
Manager, and it works, but it is a much slower connection
that it used to be. In fact, it is no faster than dial-
up, and online games refuse to connect anymore, lagging
out almost immediately.

The SBC tech support had no solution. I tried a 3rd
party "Internet Speed Booster" program, but saw no
improvement. I ran a testing utility and it gave the
following info:

Network Adapters FAILED
+ [00000001] Intel(R) PRO/100+ Management Adapter with
Alert On LAN* (PASSED)
Caption = [00000001] Intel(R) PRO/100+ Management
Adapter with Alert On LAN*
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultTTL = 0
Description = Intel(R) PRO/100+ Management Adapter with
Alert On LAN* - Packet Scheduler Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 8:14:07 PM 1/18/2038
DHCPLeaseObtained = 11:19:05 AM 9/10/2003
DHCPServer = 255.255.255.255(Invalid IP Address)
DNSEnabledForWINSResolution = FALSE
DNSHostName = samurai
Index = 1
+ IPAddress = 169.254.59.182 (PASSED)
Pinging 169.254.59.182 with 32 bytes of data:
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Ping statistics for 169.254.59.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 30
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.0.0
IPXEnabled = FALSE
KeepAliveTime = 0
MACAddress = 00:90:27:C5:BE:12
PMTUBHDetectEnabled = FALSE
PMTUDiscoveryEnabled = FALSE
ServiceName = E100B
SettingID = {8A81F08B-D3D2-43AA-A4CD-0E259A5CC901}
TcpipNetbiosOptions = 0
TcpWindowSize = 0
WINSEnableLMHostsLookup = TRUE
- [00655363] WAN Miniport (IP) (FAILED)
Caption = [00655363] WAN Miniport (IP)
DatabasePath = %SystemRoot%\System32\drivers\etc
+ DefaultIPGateway = 63.206.88.122(Same Subnet) (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
DefaultTTL = 0
Description = WAN (PPP/SLIP) Interface
DHCPEnabled = FALSE
DNSEnabledForWINSResolution = FALSE
DNSHostName = samurai
- DNSServerSearchOrder (FAILED)
+ 206.13.28.12 (FAILED)
Pinging 206.13.28.12 with 32 bytes of data:
Reply from 206.13.28.12: bytes=32 time=1722ms TTL=1722
Request timed out.
Reply from 206.13.28.12: bytes=32 time=1515ms TTL=1515
Reply from 206.13.28.12: bytes=32 time=1398ms TTL=1398
Ping statistics for 206.13.28.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 1398ms, Maximum = 1722ms, Average = 1545ms
+ 206.13.29.12 (FAILED)
Pinging 206.13.29.12 with 32 bytes of data:
Reply from 206.13.29.12: bytes=32 time=1625ms TTL=1625
Request timed out.
Reply from 206.13.29.12: bytes=32 time=1533ms TTL=1533
Reply from 206.13.29.12: bytes=32 time=1478ms TTL=1478
Ping statistics for 206.13.29.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 1478ms, Maximum = 1625ms, Average = 1545ms
GatewayCostMetric = 1
Index = 655363
+ IPAddress = 63.206.88.122 (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 50
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSubnet = 255.255.255.255
IPXEnabled = FALSE
KeepAliveTime = 0
MACAddress = 00:53:45:00:00:00
PMTUBHDetectEnabled = FALSE
PMTUDiscoveryEnabled = FALSE
ServiceName = NdisWan
TcpipNetbiosOptions = 2
TcpWindowSize = 0
WINSEnableLMHostsLookup = TRUE
- DNS Servers FAILED
- [00655363] WAN Miniport (IP) (FAILED)
- DNSServerSearchOrder (FAILED)
+ 206.13.28.12 (FAILED)
Pinging 206.13.28.12 with 32 bytes of data:
Reply from 206.13.28.12: bytes=32 time=671ms TTL=671
Request timed out.
Request timed out.
Reply from 206.13.28.12: bytes=32 time=1530ms TTL=1530
Ping statistics for 206.13.28.12:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
Approximate round trip times in milli-seconds:
Minimum = 671ms, Maximum = 1530ms, Average = 1100ms
+ 206.13.29.12 (FAILED)
Pinging 206.13.29.12 with 32 bytes of data:
Request timed out.
Reply from 206.13.29.12: bytes=32 time=1530ms TTL=1530
Reply from 206.13.29.12: bytes=32 time=1456ms TTL=1456
Reply from 206.13.29.12: bytes=32 time=1565ms TTL=1565
Ping statistics for 206.13.29.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 1456ms, Maximum = 1565ms, Average = 1517ms
+ Default Gateways PASSED
+ [00655363] WAN Miniport (IP) (PASSED)
+ DefaultIPGateway = 63.206.88.122(Same Subnet) (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
+ DHCP Servers
+ [00000001] Intel(R) PRO/100+ Management Adapter with
Alert On LAN*
DHCPServer = 255.255.255.255(Invalid IP Address)
+ IP Address PASSED
+ [00000001] Intel(R) PRO/100+ Management Adapter with
Alert On LAN* (PASSED)
+ IPAddress = 169.254.59.182 (PASSED)
Pinging 169.254.59.182 with 32 bytes of data:
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Reply from 169.254.59.182: bytes=32 time<1ms TTL=0
Ping statistics for 169.254.59.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
+ [00655363] WAN Miniport (IP) (PASSED)
+ IPAddress = 63.206.88.122 (PASSED)
Pinging 63.206.88.122 with 32 bytes of data:
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Reply from 63.206.88.122: bytes=32 time<1ms TTL=0
Ping statistics for 63.206.88.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
+ Network Clients


Any help or advice would be appreciated. Oh, both the
Ethernet card and DSL modem are nearly 4 years old now...
could it be a hardware problem? And do you find that
Cable or DSL works better with XP?
.
Click to expand...
 
Back
Top