Installing Ethenet card fails causing VXD tbl and loss of connectivity

Thanks Gary:

I agree with your assessment of a corrupts something. I've got to take a
day or so before I can get back to this problem. I'll post in a day or so
when I've got something to report.

OK. Returning to an Image of the previous is a very good idea. Unless you
want to play with this more, eg.

Then try my methodology for installing one or the other new NIC. Or accept
the other idea of simply fixing your old one (try using Duck Tape [aka duct
tape]!)

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
Thanks Gary:

I agree with your assessment of a corrupts something. I've got to take a
day or so before I can get back to this problem. I'll post in a day or so
when I've got something to report.

OK. Returning to an Image of the previous is a very good idea. Unless you
want to play with this more, eg.

Then try my methodology for installing one or the other new NIC. Or accept
the other idea of simply fixing your old one (try using Duck Tape [aka duct
tape]!)

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
Thanks Gary:

I agree with your assessment of a corrupts something. I've got to take a
day or so before I can get back to this problem. I'll post in a day or so
when I've got something to report.

accept the other idea of simply fixing your old one (try using Duck
Tape [aka duct tape]!)

Don't think I wasn't contemplating taking a soldering iron to the old card.
However, the far reaching implication here is that I no longer could add
another network type card, for example an antenna, to shed the wired
connection.

This is all somewhat academic I suppose, because this old machine is not
being used for much now. It is a Pentium II and has served me well. It's
the principle of the thing; it should work correctly. And now that this is
a spare computer,the technology and storage vehicle availabilty to create
images takes a lot of risk out of trying things. (by the way I'm using
Acronis' True Image) I'm not worried about losing anything. I can tinker
and learn.

So aside from setting this old machine up for firewall duty and maybe
putting Linux another partition for learning purposes, I'm not reluctant to
try things to have some fun and learn more.

accept the other idea of simply fixing your old one (try using Duck
Tape [aka duct tape]!)

Don't think I wasn't contemplating taking a soldering iron to the old card.
However, the far reaching implication here is that I no longer could add
another network type card, for example an antenna, to shed the wired
connection.

This is all somewhat academic I suppose, because this old machine is not
being used for much now. It is a Pentium II and has served me well. It's
the principle of the thing; it should work correctly. And now that this is
a spare computer,the technology and storage vehicle availabilty to create
images takes a lot of risk out of trying things. (by the way I'm using
Acronis' True Image) I'm not worried about losing anything. I can tinker
and learn.

So aside from setting this old machine up for firewall duty and maybe
putting Linux another partition for learning purposes, I'm not reluctant to
try things to have some fun and learn more.

Gary:

Resumed testing. Restored system to original trouble state. Installed
network printer for further tests. Was able to go to internet, network
print, and share files. Did clean boot, then followed your procedure to
remove network, recycle DUN etc. Powered down and put new card in
different slot with old card still in. Installation went off without
incident. Trouble still in and was able to share files, but not print to
the network printer. When attempting to print, got message “Could not
create socket".

Repeated the clean boot, remove network etc. Powered down, put new card in
new slot, did not put old card back. Same trouble and characteristics. It
appears that any subsequent installation clobbers TCP/IP ability to go out,
ability to communicate with other PCs intranetwork is maintained.

The network printer is on the same net as the computers but goes through
the server switch, yet Windows couldn't get a socket, nor could a laptop
that I plugged into a spare port on the print server 4-port switch
communicate.

Your thoughts on how to proceed?

Gary:

Resumed testing. Restored system to original trouble state. Installed
network printer for further tests. Was able to go to internet, network
print, and share files. Did clean boot, then followed your procedure to
remove network, recycle DUN etc. Powered down and put new card in
different slot with old card still in. Installation went off without
incident. Trouble still in and was able to share files, but not print to
the network printer. When attempting to print, got message “Could not
create socket".

Repeated the clean boot, remove network etc. Powered down, put new card in
new slot, did not put old card back. Same trouble and characteristics. It
appears that any subsequent installation clobbers TCP/IP ability to go out,
ability to communicate with other PCs intranetwork is maintained.

The network printer is on the same net as the computers but goes through
the server switch, yet Windows couldn't get a socket, nor could a laptop
that I plugged into a spare port on the print server 4-port switch
communicate.

Your thoughts on how to proceed?

Referring to the D-Link, restore the image and then, without doing a clean
boot, uninstall ICS from Windows Setup tabCommunications. Again without
bothering with a clean boot, simply uninstall all items from Network applet,
power down, replace card and, without installing any software, install
drivers directly. Put the *contents* of the Win98 folder on a floppy for
easy locating.

Do nothing else that I haven't mentioned, then report back with results.
I'll have a closer look at the D-Link software, but not until Thurs.
afternoon. No time unless I again develop insomnia. Past midnight is the
only time I can get quality computer time where I am right now, and I seem
to be cycled back to normal schedule as of this moment. My wife certainly
hopes so....

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
Gary:

Resumed testing. Restored system to original trouble state. Installed
network printer for further tests. Was able to go to internet, network
print, and share files. Did clean boot, then followed your procedure to
remove network, recycle DUN etc. Powered down and put new card in
different slot with old card still in. Installation went off without
incident. Trouble still in and was able to share files, but not print to
the network printer. When attempting to print, got message “Could not
create socket".

Repeated the clean boot, remove network etc. Powered down, put new card
in
new slot, did not put old card back. Same trouble and characteristics. It
appears that any subsequent installation clobbers TCP/IP ability to go
out,
ability to communicate with other PCs intranetwork is maintained.

The network printer is on the same net as the computers but goes through
the server switch, yet Windows couldn't get a socket, nor could a laptop
that I plugged into a spare port on the print server 4-port switch
communicate.

Your thoughts on how to proceed?

Referring to the D-Link, restore the image and then, without doing a clean
boot, uninstall ICS from Windows Setup tabCommunications. Again without
bothering with a clean boot, simply uninstall all items from Network applet,
power down, replace card and, without installing any software, install
drivers directly. Put the *contents* of the Win98 folder on a floppy for
easy locating.

Do nothing else that I haven't mentioned, then report back with results.
I'll have a closer look at the D-Link software, but not until Thurs.
afternoon. No time unless I again develop insomnia. Past midnight is the
only time I can get quality computer time where I am right now, and I seem
to be cycled back to normal schedule as of this moment. My wife certainly
hopes so....

--

Gary S. Terhune
MS-MVP Shell/User

"T. Duprex" tduprexATlandmark.net wrote in message
...
Gary:

Resumed testing. Restored system to original trouble state. Installed
network printer for further tests. Was able to go to internet, network
print, and share files. Did clean boot, then followed your procedure to
remove network, recycle DUN etc. Powered down and put new card in
different slot with old card still in. Installation went off without
incident. Trouble still in and was able to share files, but not print to
the network printer. When attempting to print, got message “Could not
create socket".

Repeated the clean boot, remove network etc. Powered down, put new card
in
new slot, did not put old card back. Same trouble and characteristics. It
appears that any subsequent installation clobbers TCP/IP ability to go
out,
ability to communicate with other PCs intranetwork is maintained.

The network printer is on the same net as the computers but goes through
the server switch, yet Windows couldn't get a socket, nor could a laptop
that I plugged into a spare port on the print server 4-port switch
communicate.

Your thoughts on how to proceed?

"Gary S. Terhune" wrote in
:

Referring to the D-Link, restore the image

Done

and then, without doing a
clean boot, uninstall ICS from Windows Setup tabCommunications.

Commutations does not have ICS, or I don't recognize what else it may
fall under. With image restored condition, under Communications I have:

Dial-up ATM support (unchecked)
Dial Up Networking (checked)
Dial-Up server (unchecked)
Direct Cable Connection (checked)
Hyper Terminal (checked)
Microsoft Chat (unchecked)
Phone Dialer (unchecked)
Universal Plug and Play (checked)
Virtual Private networking (unchecked)


Win 98:

Burned a CD. FYI, Win 98 is located at C:\ Win 98 and this location is
specified in the registry. There are no other copies Win98 cab files.


Regarding D-Link card.

This trouble condition occurs not only with the D-Link card. I have also
"installed" in a base Image condition the following:

Trendnet USB to 10/100Mbps Fast Ethernet Adapter
Airlink PCI Fast Ethernet Adapter.

Both installations triggered the no port available, inability to go
internet.

without bothering with a clean boot, simply uninstall all items from
Network applet, power down, replace card and, without installing any
software, install drivers directly.

Pending on your answer to above I'll proceed.

Put the *contents* of the Win98
folder on a floppy for easy locating.

Done.

I'll be back on line after 2 p.m.today