Walter Alcaraz
December 27th 03, 10:01 AM
Well, all, I solved my own problem.
After perusing the "microsoft.public.windowsxp.general",
"microsoft.public.windowsxp.help_and_support", and
"microsoft.public.windowsxp.network_web" newsgroups and reading messages
regarding similar problems, I tried something that another person tried and
BLING BLING! no more error message and I got me Network Connectivity again!
In fact, I'm writing this message the very laptop that didn't work.
What I did was totally uninstall McAfee ViruScan Professional Retail 7.0 and
the accompanying McAfee Firewall software applications.
I also removed all instances of "McAfee" and "Network Associates" in the
Windows Registry in both HKLM and HKCU sections.
After a system restart, everything started as normal and those services that
couldn't start before now started fine. No more "Mobile Devices Properties"
window stating that the TCP/IP network transport didn't load.
I was able to bring up IE 6 and hit several Internet web sites. I also
connected to a few file shares on the local network to make sure data could be
transferred back and forth. Everything was buzzing as normal.
I'm inferring that the trojan that whacked my laptop somehow corrupted the
McAfee TCP/IP wedge registry entry or related McAfee files associated with
McAfee ViruScan/Firewall. Un-installing the complete McAfee Suite removed
the "corrupted" wedge and/or files as well allowing TCP/IP to function
normally.
I think I'll re-enable System Restore, create a Restore Point and then
Re-Install McAfee ViruScan 7.0 Professional with Firewall.
Thank you all who made suggestions.
---- Walter
"Walter Alcaraz" > wrote in message
news:N3vHa.73087$%42.9235@fed1read06...
> I've got a major problem with Windows XP Home on my Compaq Presario 900US
> Laptop.
>
> Up until three days ago, everything was working fine. I think I got a
trojan
> or something that messed with my registry. It was one of those "PornDial"
> type programs that I think tries to set up a Dial-Up RAS connection to some
> International phone number that is the equivalent of a 900 number and
charges
> you like a billion dollars a second. Didn't hurt me since I don't use my
> modem at all, I got broadband cable. I uninstalled the trojan dialer and
> deleted all files associated with it. I ran several Virus Checkers (both
> McAfee and Symantec with latest Sig files on both) and scanned all files
> several times to make sure it was gone.
>
> Anyway, now I cannot get the network setup to work properly.
>
> Upon login I get the following window and error message:
>
> "Mobile Devices Properties" (window title)
> "The TCP/IP Network Transport is Not Installed" (error message)
>
> I am running Microsoft Windows XP with SP1 update, Internet Explorer 6.1
SP1,
> DirectX 9.0a, Windows Media Player 9, and ** ALL ** Windows Updates as of
June
> 10, 2003.
>
> Also, all Compaq Software and Drivers for the Presario 900US Laptop
installed
> as of June 2003. Versions are Windows XP WHQL certified as of June 2003.
>
> I have had this laptop/notebook since August 2002 and no problems until this
> past weekend.
>
> Note, the laptop was running fine until this little trojan type app
"infected"
> it.
>
> Now, everything ** EXCEPT ** the networking works.
>
>
> I have the following NIC/RAS adapters in my laptop:
>
> 1.) Realtek RTL8139C Fast Ethernet 10/100 MiniPCI NIC (built-in) set up as
> "Local Area Connection"
>
> 2.) Compaq Wireless MultiLan W200 802.11b set up as "Wireless Network
> Connection"
>
> 3.) Standard IEEE 1394 FireWire (built-in) set up as "1394 Connection"
>
> 4.) Conexant HSFi V.92 miniPCI Modem (built-in)
>
> The following is installed for each of the three non-modem adapters:
>
> Client for Microsoft Networks
> File and Printer Sharing
> QoS Packet Scheduler
> Microsoft Internet TCP/IP Protocol
>
>
> I have tried everything I could think of to get the network adapters working
> with TCP/IP again.
>
> 1.) I tried un-installing and reinstalling all the network adapters.
>
> 2.) I tried manually copying over fresh SP1 versions of the TCPIP files from
> the C:\windows\ServicePackFiles\i386 directory
>
> 3.) I tried disabling the Wireless 802.11b adapter and run from just the
> internal 10/100.
>
> 4.) Since you cannot uninstall TCP/IP under Windows XP, I did the equivalent
> according to the Microsoft KB article KB299357 (How to Reset Internet
Protocol
> [TCP/IP] in Windows XP). This supposedly rewrites the registry entries with
a
> clean set, using the "netsh ip reset logfile.log" command.
>
> 5.) I re-ran the Network Setup Wizard.
>
> 6.) I checked to make sure that there are no Dial-Up Networking connections
> installed.
>
> 7.) I checked Internet Properties to make sure that it is not trying to dial
> or connect to some VPN.
>
> 8.) I tried to forceably reinstall all networking drivers with latest WHQL
> versions from Compaq's site.
>
>
> None of the above worked. I still get the error message/window regarding
> Mobile Devices Properties.
>
> The network adapter drivers work properly. My 802.11b adapter can see my
> Linksys WAP fine and connects to it (verified by the SSID it gets). My
10/100
> internal MiniPCI NIC also gets a proper link when I connect it to the
Linksys
> WAP 4-port hub.
>
> Under Device Manager, it shows all Network Adapters installed fine and
enabled
> properly.
>
> However, neither the 802.11b nor the 10/100 NIC will obtain a DHCP address
> from the Linksys WAP 4-port Cable/DSL router.
>
> If I set them to static IP address on the same subnet as the Linksys
> (192.168.1.x) I still get problems. The IP's get set fine, but if I try to
> ping the internal NAT address of the Linksys router (192.168.1.1) I get
> "Destination Host Unreachable". Also, under a DOS/CLI (running the CMD.exe
> and going Command Line with ping) shell, instead of IP address or nodename
of
> destination node, I get garbage characters.
>
> Here's what the setup is:
>
> Linksys WAP 4-port router IP address 192.168.1.1
>
> Compaq WLAN 200 802.11b
> -------------------------------
> IP Address: 192.168.1.102
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.1.1
> DNS Server 1: 192.168.1.1
> DNS Server 2: not entered
>
> Realtek RTL8139C 10/100 miniPCI NIC
> ------------------------------------------
> IP Address: 192.168.1.104
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.1.1
> DNS Server 1: 192.168.1.1
> DNS Server 2: not entered.
>
> Once again, remember, this settings worked before the trojan slammed my
> laptop.
>
> SO, instead of the following:
>
> ---------------------
> C:\windows\ping 192.168.1.1
>
> pinging 192.168.1.1 with 32 bytes of data.
> ----------------------------
>
> I get
>
> ----------------------------
> pinging (!#@$%@$% garbage characters) with 32 bytes of data.
>
> Destination Host Unreachable.
> Destination Host Unreachable.
> Destination Host Unreachable.
>
> Ping statistics for (*%*@%**$# different garbage characters than above):
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).
> -----------------------------
>
> I get the same problem above regardless of whether I use the 802.11b
wireless
> or the 10/100 miniPCI NIC.
>
> I cannot do a System Restore, because I disabled it months ago, not wanting
to
> use it.
>
> Because of the thing with the TCP/IP network transport, the following
> dependent services DO NOT START:
>
> Simple TCP/IP Services
> Background Intelligent Transfer Service
> IPSEC Agent
> RIP Listener
> SSDP Discovery Service
>
>
> So, ****** WITHOUT HAVING TO REINSTALL WINDOWS XP ******,
> how do I get the damn thing working ?
>
>
> By, the way, email me at the following email address, since I don't know
when
> I can hit this newsgroup again.
>
> ================================
>
> Walter Alcaraz
>
>
> ================================
>
>
After perusing the "microsoft.public.windowsxp.general",
"microsoft.public.windowsxp.help_and_support", and
"microsoft.public.windowsxp.network_web" newsgroups and reading messages
regarding similar problems, I tried something that another person tried and
BLING BLING! no more error message and I got me Network Connectivity again!
In fact, I'm writing this message the very laptop that didn't work.
What I did was totally uninstall McAfee ViruScan Professional Retail 7.0 and
the accompanying McAfee Firewall software applications.
I also removed all instances of "McAfee" and "Network Associates" in the
Windows Registry in both HKLM and HKCU sections.
After a system restart, everything started as normal and those services that
couldn't start before now started fine. No more "Mobile Devices Properties"
window stating that the TCP/IP network transport didn't load.
I was able to bring up IE 6 and hit several Internet web sites. I also
connected to a few file shares on the local network to make sure data could be
transferred back and forth. Everything was buzzing as normal.
I'm inferring that the trojan that whacked my laptop somehow corrupted the
McAfee TCP/IP wedge registry entry or related McAfee files associated with
McAfee ViruScan/Firewall. Un-installing the complete McAfee Suite removed
the "corrupted" wedge and/or files as well allowing TCP/IP to function
normally.
I think I'll re-enable System Restore, create a Restore Point and then
Re-Install McAfee ViruScan 7.0 Professional with Firewall.
Thank you all who made suggestions.
---- Walter
"Walter Alcaraz" > wrote in message
news:N3vHa.73087$%42.9235@fed1read06...
> I've got a major problem with Windows XP Home on my Compaq Presario 900US
> Laptop.
>
> Up until three days ago, everything was working fine. I think I got a
trojan
> or something that messed with my registry. It was one of those "PornDial"
> type programs that I think tries to set up a Dial-Up RAS connection to some
> International phone number that is the equivalent of a 900 number and
charges
> you like a billion dollars a second. Didn't hurt me since I don't use my
> modem at all, I got broadband cable. I uninstalled the trojan dialer and
> deleted all files associated with it. I ran several Virus Checkers (both
> McAfee and Symantec with latest Sig files on both) and scanned all files
> several times to make sure it was gone.
>
> Anyway, now I cannot get the network setup to work properly.
>
> Upon login I get the following window and error message:
>
> "Mobile Devices Properties" (window title)
> "The TCP/IP Network Transport is Not Installed" (error message)
>
> I am running Microsoft Windows XP with SP1 update, Internet Explorer 6.1
SP1,
> DirectX 9.0a, Windows Media Player 9, and ** ALL ** Windows Updates as of
June
> 10, 2003.
>
> Also, all Compaq Software and Drivers for the Presario 900US Laptop
installed
> as of June 2003. Versions are Windows XP WHQL certified as of June 2003.
>
> I have had this laptop/notebook since August 2002 and no problems until this
> past weekend.
>
> Note, the laptop was running fine until this little trojan type app
"infected"
> it.
>
> Now, everything ** EXCEPT ** the networking works.
>
>
> I have the following NIC/RAS adapters in my laptop:
>
> 1.) Realtek RTL8139C Fast Ethernet 10/100 MiniPCI NIC (built-in) set up as
> "Local Area Connection"
>
> 2.) Compaq Wireless MultiLan W200 802.11b set up as "Wireless Network
> Connection"
>
> 3.) Standard IEEE 1394 FireWire (built-in) set up as "1394 Connection"
>
> 4.) Conexant HSFi V.92 miniPCI Modem (built-in)
>
> The following is installed for each of the three non-modem adapters:
>
> Client for Microsoft Networks
> File and Printer Sharing
> QoS Packet Scheduler
> Microsoft Internet TCP/IP Protocol
>
>
> I have tried everything I could think of to get the network adapters working
> with TCP/IP again.
>
> 1.) I tried un-installing and reinstalling all the network adapters.
>
> 2.) I tried manually copying over fresh SP1 versions of the TCPIP files from
> the C:\windows\ServicePackFiles\i386 directory
>
> 3.) I tried disabling the Wireless 802.11b adapter and run from just the
> internal 10/100.
>
> 4.) Since you cannot uninstall TCP/IP under Windows XP, I did the equivalent
> according to the Microsoft KB article KB299357 (How to Reset Internet
Protocol
> [TCP/IP] in Windows XP). This supposedly rewrites the registry entries with
a
> clean set, using the "netsh ip reset logfile.log" command.
>
> 5.) I re-ran the Network Setup Wizard.
>
> 6.) I checked to make sure that there are no Dial-Up Networking connections
> installed.
>
> 7.) I checked Internet Properties to make sure that it is not trying to dial
> or connect to some VPN.
>
> 8.) I tried to forceably reinstall all networking drivers with latest WHQL
> versions from Compaq's site.
>
>
> None of the above worked. I still get the error message/window regarding
> Mobile Devices Properties.
>
> The network adapter drivers work properly. My 802.11b adapter can see my
> Linksys WAP fine and connects to it (verified by the SSID it gets). My
10/100
> internal MiniPCI NIC also gets a proper link when I connect it to the
Linksys
> WAP 4-port hub.
>
> Under Device Manager, it shows all Network Adapters installed fine and
enabled
> properly.
>
> However, neither the 802.11b nor the 10/100 NIC will obtain a DHCP address
> from the Linksys WAP 4-port Cable/DSL router.
>
> If I set them to static IP address on the same subnet as the Linksys
> (192.168.1.x) I still get problems. The IP's get set fine, but if I try to
> ping the internal NAT address of the Linksys router (192.168.1.1) I get
> "Destination Host Unreachable". Also, under a DOS/CLI (running the CMD.exe
> and going Command Line with ping) shell, instead of IP address or nodename
of
> destination node, I get garbage characters.
>
> Here's what the setup is:
>
> Linksys WAP 4-port router IP address 192.168.1.1
>
> Compaq WLAN 200 802.11b
> -------------------------------
> IP Address: 192.168.1.102
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.1.1
> DNS Server 1: 192.168.1.1
> DNS Server 2: not entered
>
> Realtek RTL8139C 10/100 miniPCI NIC
> ------------------------------------------
> IP Address: 192.168.1.104
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.1.1
> DNS Server 1: 192.168.1.1
> DNS Server 2: not entered.
>
> Once again, remember, this settings worked before the trojan slammed my
> laptop.
>
> SO, instead of the following:
>
> ---------------------
> C:\windows\ping 192.168.1.1
>
> pinging 192.168.1.1 with 32 bytes of data.
> ----------------------------
>
> I get
>
> ----------------------------
> pinging (!#@$%@$% garbage characters) with 32 bytes of data.
>
> Destination Host Unreachable.
> Destination Host Unreachable.
> Destination Host Unreachable.
>
> Ping statistics for (*%*@%**$# different garbage characters than above):
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).
> -----------------------------
>
> I get the same problem above regardless of whether I use the 802.11b
wireless
> or the 10/100 miniPCI NIC.
>
> I cannot do a System Restore, because I disabled it months ago, not wanting
to
> use it.
>
> Because of the thing with the TCP/IP network transport, the following
> dependent services DO NOT START:
>
> Simple TCP/IP Services
> Background Intelligent Transfer Service
> IPSEC Agent
> RIP Listener
> SSDP Discovery Service
>
>
> So, ****** WITHOUT HAVING TO REINSTALL WINDOWS XP ******,
> how do I get the damn thing working ?
>
>
> By, the way, email me at the following email address, since I don't know
when
> I can hit this newsgroup again.
>
> ================================
>
> Walter Alcaraz
>
>
> ================================
>
>