Run Winsock on Win 3.1 NT client

I have a Win3.1 NT client with NETBEIU connecting to a NT server. Now I want to connect my computer to Internet over a LAN, so I have to install Trumpet winsock in order to run mail client or Telnet client etc on my computer.
How can I change my set up to achieve the above?
I've tried to add a packet drive to the protocol.ini but failed. Please explain your answer in details. Thank you.

My previous description to the problem (as above) may cause some misleadings. Let me be more specific to the question.
My desktop is running Windows 3.1 and connecting to a NT server using
"NT client for DOS". It works fine when multiprotocols are used.
Now I want to connect my desktop via a LAN (to a Unix server connected to the Internet instead of a modem) and use winsock mail, ftp clients etc.
Those clients have to be running on winsock. Then I installed a packet driver by changing my autoexec.bat (referring to the sample as below. However, both connections to NT server and the 'Internet server' were broken. I feel my settings are not quite right.

----original settings ----
[config.sys]
device=D:\NET\ifshlp.sys
LASTDRIVE=Z

[autoexec.bat]
SET PATH=D:\NET
D:\NET\net start

the rest are not listed....

----new settings------
[autoexec.bat]
SET PATH=D:\NET
....
d:\net\3c5x9pd -w 0x60 iobase=0x300
d:\net\winpkt 0x60
....
D:\NET\net start

slbyeungAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

slbyeungAuthor Commented:
Edited text of question
0
os012897Commented:
Hmmm ..... I never used NT version 3.1 so I wonder whether it has
its own Microsoft TCP/IP stack (NT4.0 and win95 have that). In
case NT3.1 is shipped with a microsoft tcp/ip stack, than you
should use it! If it is not, then use Trumpet winsock. I used them for win3.1 (not NT though) and they worked ok.
All I had to do was to configure it with ip, gateway etc. settings and to put them into the autostart-group. You should not
need to edit protocol.ini yourself!

On some of our NT4.0 machines we have Microsoft TCP/IP and NetBeui running without problems of interferance between those
two protocols. If you encounter problems with your network-access
after installing Trumpet, probably consider removing NetBeui
(TCP/IP is by far superiour to it anyway) ....

Hope that helps

Regards,

       os

0
slbyeungAuthor Commented:
Edited text of question
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

slbyeungAuthor Commented:
Edited text of question
0
slbyeungAuthor Commented:
Edited text of question
0
slbyeungAuthor Commented:
please refer to the question fro more precise description
0
os012897Commented:
Ok, lets see .....

Make sure the packet-driver of oyur net-card "3c5x9pd" loads
without errors, and winpkt too!

You are loading your net-card-driver with an "-w" option. On my
driver this was a patch to run under windows too, which should
NOT be used in conjunction with winpkt. So if this is the case
with your driver too, remove the option!

Try to omit the io_base-address as the driver usually finds the
right one out by himself.

I used the "nwpd"-net-card driver which seems to work for a great
variety of different cards. You could try to use it instead of
your "3c5x9pd" driver.

\net\nwpd.com 0x60   // nwpd usually gets the io_base by himself
\net\winpkt.com 0x60

Make sure your settings in tcpman are correct, do not change
more than you have for the beginning. For a start try to
connect to a simple service like ftp or telnet without using
name-servers or thelike. e.g. ftp 123.54.100.46 .....

Temporarily disabling your "nt client for dos" protocol
could probably help in finding the problem ..... for TCP/IP
the only thing you need in autoexec.bat are the two lines with
the packet-drivers, no additions in config.sys are needed!!

If it still does not work, please report the exact error that
tcpman is reporting on starup or that you get by your application!

Regards,

          os

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.