Solved

Why can't I connect a DOS client to NT with MS Client 3.0?

Posted on 1997-06-06
2
315 Views
Last Modified: 2013-12-23
I am trying to connect a DOS client to NT server using NWlink and Microsoft Client for MS-DOS v.3.0.  I can't get the client to find the NT server, although the NT server appears and is accessible to Win 95 and Win NT workstations on the network.  The network is currently running NetWare 3.12.  DOS Client v.3.0 can't find the NetWare 3.12 server either.  The DOS PCs can all find the NetWare server using VLM.  I think that NWlink is enabled on the server; at least it says so in Control Panel on the server.

What, precisely, does one have to do on the server end and on the client end to get the DOS client software to connect to the server using NWlink?
0
Comment
Question by:Wkiernan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 2

Accepted Solution

by:
eizens earned 100 total points
ID: 1560613
It seems that you have no the same frame type on the client side and on the server. If so...
   If you have NetWare 3.12 server on network, frame type may be either 802.3, either 802.2. When you installed NWlink on the NT server, it autodetected frame from network and is using it.
Therefore You have to try with different frame settings (default installation usually installs all four frames -- .2 .3 II and .SNAP. You will never need .SNAP, and .II is needed if you use TCP/IP on your network. Therefore you need to check two variants.
But when you check, remove other frame types, session is established using first frame type.
    I hope, it's your's only problem.
Best regards, Eizens

0
 

Author Comment

by:Wkiernan
ID: 1560614
Hello eizens!  I was using 802.2 on the NetWare 3.12 server, in NWlink on the NT Server it was set to Auto-detect, and on the DOS client stuff it was set to 802.2.  I gave up on NWlink and tried NetBEUI, and the DOS client was able to connect to the NT server, but, of course, not to the NetWare server.  I happened to go look at the NetWare server console, and I saw an error message about how a router (NT) had mis-identified the internal network number.  It turns out that if I change the internal network number in NT to match the internal network number of the NetWare server, I can now use either NetBEUI or NWlink to connect the DOS client to the NT server using the MS Network Client v.3.0; I still can't see the NetWare server from the DOS client, but I haven't enabled Gateway service for NetWare on the NT server yet.  (I have to figure out a couple of problems concerning access permissions first.) Thanks for your help; you're the first person who has been willing to talk to me about this problem.

Yours WDK - WKiernan@concentric.net
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
Resolve DNS query failed errors for Exchange
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question