Communication problem involving NetTrans?

My old standalone Win98SE machine has always connected to the Internet
(cable modem) just fine. Recently I tried to connect this machine to a
network via a Linksys router, and botched the installation of the
software. As a result, the machine will no longer communicate with
*anything* via the Ethernet port. I would like to get it back to the
original standalone condition, but I am unable to do so.

I have reloaded Windows. I have removed and reloaded all the networking
components at Control Panel/Network. These components are Client for MS
Networks, Dial Up Adapter, Ethernet Adapter, TCP/IP for each adapter,
and File & Printer Sharing for MS Networks. Nothing else. Never had
NetBeui, IPX, or Netware - still don't. I have confirmed that all the
settings for those components are exactly as they were before. However,
I do notice that I am no longer asked to log in at bootup, even though
my Primary Network Logon is set to Client for Microsoft Networks.

Device Manager assures me that the Ethernet card is working properly
and there are no conflicts, but just to be sure, I bought and installed
a new one. And the green and yellow LEDs at both ends of the Ethernet
cable light up. However, each attempt to go out to thre Internet
results in a long "Resolving host" indication, followed by "Failed to
connect to server", on each of several servers that I am set up for. Or
a timeout if I try to ping. BTW, if another machine is plugged into the
same cable modem with the same Ethernet cable, it works fine.

The problem seems to lie in something called NetTrans. If I go to
Accessories/SystemTools/SystemInformation/Components/Network, it tells
me that TCP/IP-NetTrans-...-0000 (presumably for the DialUp Adapter) is
OK, but under TCP/IP-NetTrans-...-0001, I see "This Device Has A Problem
- Code=11 (0xB). Try reinstalling the driver."
Then it lists Registry Key HKEY_LOCAL_MACHINE\enum\NETWORK\MSTCP\0001.
Then it says "None" for all five resources.
Then it lists several drivers. The first is
NetTrans\0001. In accordance with KB 193637, I extracted another
copy of Nettrans.inf from my CD to C:\windows\inf.
The other listed drivers are
netbeui.vxd
vnbt.386
vdhcp.386
vtcp.386
vip.386
vtdi.386
None of this has brought my communications back. Am I following the
wrong leads? Why am I no longer asked to log in at bootup? What should
the registry entries at the cited registry key look like? By the way,
NetTrans is referred to as a "device", but it is not a hardware device,
is it?

Any help gratefully received.

Bill Jeffrey
--
Remove NOSPAM from my address before e-mailing a reply.
Outgoing mail is automatically scanned by Norton Anti-Virus.

Bill Jeffrey wrote:

> My old standalone Win98SE machine has always connected to the Internet
> (cable modem) just fine. Recently I tried to connect this machine to a
> network via a Linksys router, and botched the installation of the
> software. As a result, the machine will no longer communicate with
> *anything* via the Ethernet port. I would like to get it back to the
> original standalone condition, but I am unable to do so.
>
> I have reloaded Windows. I have removed and reloaded all the networking
> components at Control Panel/Network. These components are Client for MS
> Networks, Dial Up Adapter, Ethernet Adapter, TCP/IP for each adapter,
> and File & Printer Sharing for MS Networks. Nothing else. Never had
> NetBeui, IPX, or Netware - still don't. I have confirmed that all the
> settings for those components are exactly as they were before. However,
> I do notice that I am no longer asked to log in at bootup, even though
> my Primary Network Logon is set to Client for Microsoft Networks.
>
> Device Manager assures me that the Ethernet card is working properly
> and there are no conflicts, but just to be sure, I bought and installed
> a new one. And the green and yellow LEDs at both ends of the Ethernet
> cable light up. However, each attempt to go out to thre Internet
> results in a long "Resolving host" indication, followed by "Failed to
> connect to server", on each of several servers that I am set up for. Or
> a timeout if I try to ping. BTW, if another machine is plugged into the
> same cable modem with the same Ethernet cable, it works fine.
>
> The problem seems to lie in something called NetTrans. If I go to
> Accessories/SystemTools/SystemInformation/Components/Network, it tells
> me that TCP/IP-NetTrans-...-0000 (presumably for the DialUp Adapter) is
> OK, but under TCP/IP-NetTrans-...-0001, I see "This Device Has A Problem
> - Code=11 (0xB). Try reinstalling the driver."
> Then it lists Registry Key HKEY_LOCAL_MACHINE\enum\NETWORK\MSTCP\0001.
> Then it says "None" for all five resources.
> Then it lists several drivers. The first is
> NetTrans\0001. In accordance with KB 193637, I extracted another
> copy of Nettrans.inf from my CD to C:\windows\inf.
> The other listed drivers are
> netbeui.vxd
> vnbt.386
> vdhcp.386
> vtcp.386
> vip.386
> vtdi.386
> None of this has brought my communications back. Am I following the
> wrong leads? Why am I no longer asked to log in at bootup? What should
> the registry entries at the cited registry key look like? By the way,
> NetTrans is referred to as a "device", but it is not a hardware device,
> is it?
>
> Any help gratefully received.
>
> Bill Jeffrey
After reading an answer in a different thread, I found and removed an
AutoLogon entry in the Registry. No idea where it came from, but now I
get properly logged in again. I also extracted and reloaded all of the
other drivers listed above. Still no joy, though.

Bill

--
Remove NOSPAM from my address before e-mailing a reply.
Outgoing mail is automatically scanned by Norton Anti-Virus.

Bill Jeffrey wrote:
> Bill Jeffrey wrote:
>
>> My old standalone Win98SE machine has always connected to the Internet
>> (cable modem) just fine. Recently I tried to connect this machine to
>> a network via a Linksys router, and botched the installation of the
>> software. As a result, the machine will no longer communicate with
>> *anything* via the Ethernet port. I would like to get it back to the
>> original standalone condition, but I am unable to do so.
>>
>> I have reloaded Windows. I have removed and reloaded all the networking
>> components at Control Panel/Network. These components are Client for
>> MS Networks, Dial Up Adapter, Ethernet Adapter, TCP/IP for each
>> adapter, and File & Printer Sharing for MS Networks. Nothing else.
>> Never had
>> NetBeui, IPX, or Netware - still don't. I have confirmed that all the
>> settings for those components are exactly as they were before.
>> However, I do notice that I am no longer asked to log in at bootup,
>> even though my Primary Network Logon is set to Client for Microsoft
>> Networks.
>>
>> Device Manager assures me that the Ethernet card is working properly
>> and there are no conflicts, but just to be sure, I bought and
>> installed a new one. And the green and yellow LEDs at both ends of
>> the Ethernet cable light up. However, each attempt to go out to thre
>> Internet results in a long "Resolving host" indication, followed by
>> "Failed to connect to server", on each of several servers that I am
>> set up for. Or a timeout if I try to ping. BTW, if another machine is
>> plugged into the same cable modem with the same Ethernet cable, it
>> works fine.
>>
>> The problem seems to lie in something called NetTrans. If I go to
>> Accessories/SystemTools/SystemInformation/Components/Network, it tells
>> me that TCP/IP-NetTrans-...-0000 (presumably for the DialUp Adapter)
>> is OK, but under TCP/IP-NetTrans-...-0001, I see "This Device Has A
>> Problem - Code=11 (0xB). Try reinstalling the driver."
>> Then it lists Registry Key HKEY_LOCAL_MACHINE\enum\NETWORK\MSTCP\0001.
>> Then it says "None" for all five resources.
>> Then it lists several drivers. The first is
>> NetTrans\0001. In accordance with KB 193637, I extracted another
>> copy of Nettrans.inf from my CD to C:\windows\inf.
>> The other listed drivers are
>> netbeui.vxd
>> vnbt.386
>> vdhcp.386
>> vtcp.386
>> vip.386
>> vtdi.386
>> None of this has brought my communications back. Am I following the
>> wrong leads? Why am I no longer asked to log in at bootup? What
>> should the registry entries at the cited registry key look like? By
>> the way, NetTrans is referred to as a "device", but it is not a
>> hardware device, is it?
>>
>> Any help gratefully received.
>>
>> Bill Jeffrey
>
> After reading an answer in a different thread, I found and removed an
> AutoLogon entry in the Registry. No idea where it came from, but now I
> get properly logged in again. I also extracted and reloaded all of the
> other drivers listed above. Still no joy, though.
>
> Bill
>
Gettin' kinda lonesome in this thread. I guess I should have posted in
the standard format - like

Subject: Help
Body text: My computer doesn't work right. What should I do?

Seriously, guys, have I violated some point of etiquette here? Am I
wearing an ugly tie? Or is this one of those problems that's just too
hard to troubleshoot remotely? I thought that by outlining the problem
and symptoms thoroughly, and providing information on the things I had
tried, it would help the process speed to a quick solution. Not so?

Still slogging my way through it ...
Bill Jeffrey

--
Remove NOSPAM from my address before e-mailing a reply.
Outgoing mail is automatically scanned by Norton Anti-Virus.

Try this: www.careyholzman.com/netfixes.htm

Carey

"Bill Jeffrey" <(E-Mail Removed)> wrote in message
news:tmmEb.17262$J77.6681@fed1read07...
> My old standalone Win98SE machine has always connected to the Internet
> (cable modem) just fine. Recently I tried to connect this machine to a
> network via a Linksys router, and botched the installation of the
> software. As a result, the machine will no longer communicate with
> *anything* via the Ethernet port. I would like to get it back to the
> original standalone condition, but I am unable to do so.
>
> I have reloaded Windows. I have removed and reloaded all the networking
> components at Control Panel/Network. These components are Client for MS
> Networks, Dial Up Adapter, Ethernet Adapter, TCP/IP for each adapter,
> and File & Printer Sharing for MS Networks. Nothing else. Never had
> NetBeui, IPX, or Netware - still don't. I have confirmed that all the
> settings for those components are exactly as they were before. However,
> I do notice that I am no longer asked to log in at bootup, even though
> my Primary Network Logon is set to Client for Microsoft Networks.
>
> Device Manager assures me that the Ethernet card is working properly
> and there are no conflicts, but just to be sure, I bought and installed
> a new one. And the green and yellow LEDs at both ends of the Ethernet
> cable light up. However, each attempt to go out to thre Internet
> results in a long "Resolving host" indication, followed by "Failed to
> connect to server", on each of several servers that I am set up for. Or
> a timeout if I try to ping. BTW, if another machine is plugged into the
> same cable modem with the same Ethernet cable, it works fine.
>
> The problem seems to lie in something called NetTrans. If I go to
> Accessories/SystemTools/SystemInformation/Components/Network, it tells
> me that TCP/IP-NetTrans-...-0000 (presumably for the DialUp Adapter) is
> OK, but under TCP/IP-NetTrans-...-0001, I see "This Device Has A Problem
> - Code=11 (0xB). Try reinstalling the driver."
> Then it lists Registry Key HKEY_LOCAL_MACHINE\enum\NETWORK\MSTCP\0001.
> Then it says "None" for all five resources.
> Then it lists several drivers. The first is
> NetTrans\0001. In accordance with KB 193637, I extracted another
> copy of Nettrans.inf from my CD to C:\windows\inf.
> The other listed drivers are
> netbeui.vxd
> vnbt.386
> vdhcp.386
> vtcp.386
> vip.386
> vtdi.386
> None of this has brought my communications back. Am I following the
> wrong leads? Why am I no longer asked to log in at bootup? What should
> the registry entries at the cited registry key look like? By the way,
> NetTrans is referred to as a "device", but it is not a hardware device,
> is it?
>
> Any help gratefully received.
>
> Bill Jeffrey
> --
> Remove NOSPAM from my address before e-mailing a reply.
> Outgoing mail is automatically scanned by Norton Anti-Virus.
>