Solved

PROBLEMS CONFIGURING BROADBAND WITH NDISWAN

Posted on 2003-10-27
5
628 Views
Last Modified: 2013-12-27
I HAVE INSTALLED A BT VOYAGER 100 ADSL MODEM, IT IS WORKING FINE ACCORDING TO DEVICE MANAGER, BUT I UNDERSTAND THAT IT NEEDS TO BE CONFIGURED TO USE NDISWAN.  I CAN FIND THESE FILES USING A SEARCH BUT THE DRIVERS ARE NOT AVAILABLE IN PROTOCOLS.  HOW DO I RE-INSTALL THIS PROTOCOL.
0
Comment
Question by:rospat2
  • 2
5 Comments
 
LVL 2

Expert Comment

by:drdave35
ID: 9662229
NDISWAN reconfiguration will require you to uninstall and reinstall your TCP/IP stack.

Go to My Network Places, right click, go to properties, and remove TCP/IP protocol which is bound to your NIC in use by the modem.  First, make certain you copy down all of the settings in order to re-input them upon reinstall.

You may need your XP disk, just in case. Use if only if called for.

Once you remove the service, reboot your machine (not mandatory, but helpful) and go back into My Network Places, properties, and add TCP/IP back in.

There is no direct way to add NDISWAN, as, it is a part of a protocol, not an installable option.

Also, make certain your ISP is not using PPOE.  If it is, you must configure those settings as well.

Are you using a router/firewall?  If so, go into the router setup page and verify your logon information and PPOE configuration according to the specifications supplied by your ISP.

Hope this helps.

Dave Smiler, MCSE
0
 

Author Comment

by:rospat2
ID: 9665524
Thanks Dave

When I go into the properties I cannot uninstall TCP/IP as the uninstall option is not highlighted.  Any ideas how I can do this?

Ros
0
 
LVL 2

Accepted Solution

by:
drdave35 earned 500 total points
ID: 9668777
Okay...it isn't pretty, but here it is!  Be careful to follow the Knowledge Base info exactly.

Here's the link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;299357&Product=WINME

Microsoft Knowledge Base Article - 299357    
 
 
Support Centers
 Windows XP  
 

How to Reset Internet Protocol (TCP/IP) in Windows XP
View products that this article applies to.
This article was previously published under Q299357
SUMMARY
When viewing the list of components for a network interface, you may notice that the Uninstall button is disabled when Internet Protocol (TCP/IP) is selected. In Windows XP, the TCP/IP stack is considered a core component of the operating system; therefore, it is not possible to uninstall TCP/IP in Windows XP.

In extreme cases, reinstalling the Internet Protocol stack may be the most appropriate solution. With the NetShell utility, you can now reset the TCP/IP stack back to a pristine state, to the same state as when the operating system was installed.
MORE INFORMATION
The NetShell utility (netsh) is a command-line scripting interface for the configuring and monitoring of Windows XP networking. This tool provides an interactive network shell interface to the user.

In Windows XP, a reset command is available in the IP context of the NetShell utility. When this command is executed, it rewrites pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to achieve the same result as the removal and the reinstallation of the protocol.
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
SYSTEM\CurrentControlSet\Services\DHCP\Parameters\
                        
Command Usage
netsh int ip reset [log_file_name]

To successfully execute the command, you must specify a log file name where actions taken by netsh will be recorded. For example, typing either of the examples that are listed in the "Command Samples" section later in this article at a command prompt would reset the TCP/IP stack on a system and record the actions that were taken in the log file, Resetlog.txt. The first sample creates the log file in the current directory, while the second sample demonstrates the use of a path where the log will be created. In either case, where the specified log file already exists, the new log will be appended to the end of the existing file.
Command Samples
netsh int ip reset resetlog.txt
netsh int ip reset c:\resetlog.txt

Sample Log File for NETSH INT IP RESET
The following is a sample of the log file that is generated by netsh when an IP reset command is issued. The actual log file may vary depending on the configuration of the system on which the command is issued. In some cases, there may be no actions logged in the file, which typically is the case when the TCP/IP registry keys have not been altered from their original configuration.
reset   SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\Options\15\RegLocation
            old REG_MULTI_SZ =
                SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\?\DhcpDomain
                SYSTEM\CurrentControlSet\Services\TcpIp\Parameters\DhcpDomain

added   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\NetbiosOptions
added   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{BAA9D128-54BB-43F6-8922-313D537BE03E}\NetbiosOptions
reset   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\NameServerList
            old REG_MULTI_SZ =
                10.1.1.2

deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\AddressType
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\DefaultGatewayMetric
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\DisableDynamicUpdate
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\DontAddDefaultGateway
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\EnableDhcp
            old REG_DWORD = 0

added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\NameServer
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\RawIpAllowedProtocols
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\TcpAllowedPorts
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{2DDD011E-B1B6-4886-87AC-B4E72693D10C}\UdpAllowedPorts
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\DisableDynamicUpdate
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\EnableDhcp
            old REG_DWORD = 0

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\IpAddress
            old REG_MULTI_SZ =
                12.12.12.12

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\IpAutoconfigurationSeed
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\RawIpAllowedProtocols
            old REG_MULTI_SZ =
                0

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\SubnetMask
            old REG_MULTI_SZ =
                255.255.255.0

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\TcpAllowedPorts
            old REG_MULTI_SZ =
                0

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5B3675C3-6EB9-4936-B991-04DA31024C4E}\UdpAllowedPorts
            old REG_MULTI_SZ =
                0

added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\AddressType
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\DefaultGatewayMetric
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\DisableDynamicUpdate
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\DontAddDefaultGateway
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\EnableDhcp
            old REG_DWORD = 0

added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\NameServer
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\RawIpAllowedProtocols
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\TcpAllowedPorts
added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BAA9D128-54BB-43F6-8922-313D537BE03E}\UdpAllowedPorts
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\DefaultGateway
            old REG_MULTI_SZ =
                10.1.1.2
               

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\DefaultGatewayMetric
            old REG_MULTI_SZ =
                0
               

added   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\DisableDynamicUpdate
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\EnableDhcp
            old REG_DWORD = 0

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\IpAddress
            old REG_MULTI_SZ =
                10.1.1.1
               

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\IpAutoconfigurationSeed
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\NameServer
            old REG_SZ = 10.1.1.2,10.1.1.3

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\RawIpAllowedProtocols
            old REG_MULTI_SZ =
                0

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\SubnetMask
            old REG_MULTI_SZ =
                255.255.255.0
               

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\TcpAllowedPorts
            old REG_MULTI_SZ =
                0

reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}\UdpAllowedPorts
            old REG_MULTI_SZ =
                0

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution
<completed>
                        
The information in this article applies to:
Microsoft Windows XP Professional
Microsoft Windows XP Home Edition
Last Reviewed: 10/30/2003 (1.1)  
Keywords: kbenv kbhowto kbnetwork KB299357

 
 
© 2003 Microsoft Corporation. All rights reserved.  Terms of use  Security & Privacy  Accessibility  


You might want to grab an updated version of your NIC's installation software and drivers before trying the above.  They will  install updated versions of NDISWAN for their own purposes, and it may have a beneficial effect on your network connection.

Let me know how this works.

Dave Smiler, MCSE
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Dell M6220 to Dell 6224 Port channel conundrum 5 21
Soddering on the board 11 109
Cisco IOU High CPU Usuage 6 78
nipper studio 2 5
Hello All, I have been training on Multicast for a while now and whenever I start the topic , I find out that my friends /  Colleagues mention that they do not know how to test Multicast Joins. As most of the multicast would be video traffic and …
Hi there, This article summarizes what you need if you are going to set up your home or small business Network Attached Storage (NAS) to be accessible from the internet. Of course there are configuration differences based on your NAS or router ma…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now