d-link AND dynalink installation woes

Hi, I'm having trouble connecting my optusnet d-link 302g adsl modem in windows xp.
Installation aborts with an error message to check connections. They seem OK & my modem is shown as connected. Ipconfig results in both ip address and subnet mask as 0.0.0.0. Cannot ping any sites. Cannot access modem interface. Have tried with a different USB cable, also LAN with the same results. Also, reset the modem to default settings then re-installed. No firewalls or other programs running to cause interference. With USB connection, if I set TCP/IP to 10.1.1.10, then I can connect to the modem interface through 10.1.1.2. But cannot access any internet sites. Haven't managed this with the ethernet connection. In TCP/IP properties, have tried entering optusnet's primary & secondary DNS to no avail. Also tried enabling NAT from modem interface. Nothing works. However, the modem is OK as it works fine in an older machine with Windows 98. Interestingly, a friend has exactly the same problem trying to set up his bigpond dynalink modem also in windows XP. Both bigpond's & optus tech support can see our modems as connected. And both reckon that it's a windows setting (possibly one of the background services) that causes our problems. So far as I can tell, the only thing that our machines have in common is that both are configured for 'closed netbios' operation (courtesy of Steve Gibson's app).We also had his other security apps installed but have disabled them. A couple of geriatrics would really appreciate some guidance as to how to overcome our mutual problem.

 

Peter - at this point I suggest a clean start. The various bindings tricks from the Gibson "Shields Up" article I just read are OK I suppose but if not done just so, can cause all sorts of strange problems. After we get things running, you can tweak some if you want but you will have working basics to go back to.

I'm assuming here that you have one PC that you want to connect directly to the DSL modem. If not (if you have a router/switch for instance) please say what one you have since the setup will be different.

For now do the following and since I read you have the option of Ethernet (the network card with the connection that looks like an oversize phone plug), lets get that one working. USB is great for most anything other than networking and usually OK for that but when it has problems, is a real bear to diagnose and fix.

Any time you see words in bold and connected with ~ it means do each of things so start~run~cmd would be to click on Start, click on Run, type in CMD and press ENTER.

• Right-click on the My Network Places icon then Properties and remove all the devices you have now. Close the window.
• start~run~cmd should open a "DOS" style window with a command prompt where you can type stuff
• netsh int ip reset c:\ipreset-log.txt this is one long command you need to type and note the spaces. It resets your TCP/IP values to the defaults since XP won't allow removal and reinstall of TCP/IP
• Exit and the cmd window should close
• Right-click My Computer, left-click manage, double-click Device Manager. When it opens, remove any network adapters you find and close device manager.
• Reboot and let the system find & set up your network adapter again.
• Go through the modem setup instructions your ISP has provided as if you'd never done the setup before.
• When the setup is finished and regardless of if it is working or not, start~run~cmd followed by ipconfig /all > c:\ipconfig.txt note the spaces after ipconfig, after /all, and after >

At this point if things are working, you will have a couple of small text files you don't need. However, if all is not well then use notepad to open c:\ipreset-log.txt, copy the contents and paste here. Do the same with c:\ipconfig.txt.

Not sure how geriatric you two are. Me, I'm a spring chick who won't even turn 60 for another few months but happy to help the older generation whenever I can.

 

Many thanks, Newt
will follow your detailed instructions later today, and post back.
BTW - am just nudging 76 (spring chook? 2nd childhood.?
moderately experienced, but this had me stumped. I'd suspected the
gibson tweaks, but hadn't a clue how to fix. Your advice is just what I need.
Thanks again

 

Hope it fixes you up but if not, we'll keep banging away at it until things are working like they should.

 

Hi! Me again with no joy to report - followed all steps but modem failed.
log files are
reset-log.txt

reset SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{50BDEA9B-5D05-4FED-B4F8-194AE54ED986}\NameServerList
old REG_MULTI_SZ =<empty>
added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{50BDEA9B-5D05-4FED-B4F8-194AE54ED986}\NetbiosOptions

reset SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{6EF5A406-F111-4C17-ACAF-89454C007C78}\NameServerList
old REG_MULTI_SZ =<empty>
added SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{6EF5A406-F111-4C17-ACAF-89454C007C78}\NetbiosOptions

deleted
SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts

deleted
SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableProxy

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{50BDEA9B-5D05-4FED-B4F8-194AE54ED986}\NameServer

added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5E5C010B-E4B4-43B6-A88D-0DD8E5C442F3}\AddressType

added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5E5C010B-E4B4-43B6-A88D-0DD8E5C442F3}\DisableDynamicUpdate

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5E5C010B-E4B4-43B6-A88D-0DD8E5C442F3}\RawIpAllowedProtocols
old REG_MULTI_SZ =0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5E5C010B-E4B4-43B6-A88D-0DD8E5C442F3}\TcpAllowedPorts
old REG_MULTI_SZ =0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{5E5C010B-E4B4-43B6-A88D-0DD8E5C442F3}\UdpAllowedPorts
old REG_MULTI_SZ =0

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{6EF5A406-F111-4C17-ACAF-89454C007C78}\NameServer


added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\AddressType


reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\DefaultGateway
old REG_MULTI_SZ =203.2.75.132

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\DefaultGatewayMetric
old REG_MULTI_SZ =0

added SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\DisableDynamicUpdate

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\EnableDhcp
old REG_DWORD = 0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\IpAddress
old REG_MULTI_SZ =10.1.1.10

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\RawIpAllowedProtocols
old REG_MULTI_SZ =0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\SubnetMask
old REG_MULTI_SZ =255.0.0.0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\TcpAllowedPorts
old REG_MULTI_SZ =0

reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{A1A9768A-7B88-4C8F-985E-6FCE82D5D789}\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\TcpWindowSize

deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution

reset
Linkage\UpperBind for PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\3&61AAA01&0&68. bad value was:
REG_MULTI_SZ =PSched

reset Linkage\UpperBind for USB\VID_07D1&PID_13F1\555. bad value was:
REG_MULTI_SZ =PSched

reset Linkage\UpperBind for PCI\VEN_1282&DEV_9102&SUBSYS_00000000&REV_10\3&61AAA01&0&60. bad value was:
REG_MULTI_SZ =PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =PSched

<completed>

ipconfig.txt

Windows IP Configuration
Host Name . . . . . . . . . . . . : ipex
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 10:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC #2
Physical Address. . . . . . . . . : 00-40-95-30-F1-D7
Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
IP Address. . . . . . . . . . . . : fe80::240:95ff:fe30:f1d7%4
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

 

Well, the reset appears to have gone OK.

The rest of it is a little confusing though.

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC #2

With a NIC #2 I would expect to see a NIC #1 and the ipconfig /all should have shown both.

Really not sure where the IP-V6 data populated from (IP Address. . . : fe80::240:95ff:fe30:f1d7%4 and the other similar ones) but since your ISP is surely still using IP-V4 data, the IP-V6 stuff shouldn't help or hurt.

Some other information that should have displayed is just plain missing.

After the reset, you should have just needed to name your PC with whatever name the ISP specified and then in Control Panel

- Network and Internet Connections

- Set Up or Change my Home Network Settings

- This computer connects directly to the Internet. I do not have a home network yet

Is that pretty much how things went?

 

Hi Newt - back again after a ouple of days time out. Thanks for your interest & help so far. But there's still a way to go. The adsl installation is automatic from a CD. Manual instructions are simply to set to auto obtain IP address and DNS.
No computer name necessary - simply add user name, pwd, and real name in appropriate fields, which are then configured into the modem. But modem can't be found. Followed your suggestion to manually change/setup home network settings, but this didn't work. As previously noted, if I give TCP/IP an address (10.1.1.10 - I can access tthe modem page at 10.1.1.1, but can't see the internet altho' the modem is connected. Also found and entered primary & secondary DNS addresses but no luck there. I successfully installed the adsl on a borrowed 'clean' XP computer and compared settings. All settings seemed the same. Gateway was the same as the assigned sessional IP address, so no point in trying to add that to the settings. There were two services running on that machine which weren't on mine. DHCP client & TCP/IP NetBios helper. Both are set to auto start. An attempt to manually start them in my machine resulted in ' . . .failed to start. The dependency service or group failed to start'.
Dependencies are:

DHCP client
AFD Networking support
NetBios over tcpip
TCP/IP protocol driver
TCP/IP protocol driver
IPSEC driver

TCP/IP NetBios helper dependencies:
AFD Networking support
NetBios over tcpip
TCP/IP protocol driver
IPSEC driver.

These 2 services auto started OK on my machine:

DNS client (& dependencies)
TCP/IP protocol driver
IPSEC driver

IPSEC services
IPSEC driver
Remote Procedure Call
TCP/IP protocol driver
IPSEC driver

It looks as tho' the AFD networking support may be the critical component, at least a clue to what's going on. But how to restore it? I know not.

 

Not ignoring you Peter. Just need to do some research on this and won't have time until some time this evening.

 

That's OK Newt. I appreciate you fitting my query into your undoubtedly busy schedule whenever you can. My problem ain't gonna go 'way cobber (dinkum Aussie for 'mate'). I've read some of your other responses & I admire the dedication you display in helping those in trouble.

 

I dood it! !!!
After niggling at the problem for a while, I finally was able to check settings on a successful connection on another XP machine. Found & noted appropriate settings, then a lengthy edit registry session. Lo & behold it worked
Thanks Newt for your input.