drive map NTW4 to NTSvr4\different IP groups

Posted on 1998-03-31
Last Modified: 2013-12-23
I resently upgraded to NT 4 Workstation from Win95 and wish to map drives to some NT Servers i have. I could connect to the servers under 95 but now can't see them. The servers have  internet IP addresses and i have an
internal 192 address. I am running TCP\IP and NetBEUI, the servers are running the same protocols.
I can ping the servers using their addresses and with their names. Yet i can't see them in the network neighbourhood. I can see all the other Win95 pc's on the network, but not my servers.
If i can ping them then why can't i connect to them? if i try  it manually using "net use \\realtime1\rt1_cdriv" it
comes up with error 53.
Question by:adriand033198
  • 3

Author Comment

ID: 1571701
Adjusted points to 50

Author Comment

ID: 1571702
Adjusted points to 100

Expert Comment

ID: 1571703
Try the following:
Start-Run- enter: \\servername
You should get a list of all network shares of this server.
at the DOS-Prompt enter: net view -> you get a list of all servers and WS in your domain/workgroup,
net view \\servername -> same as the first test (see above )

Accepted Solution

biyiadeniran earned 110 total points
ID: 1571704
When you attempt to connect to a Fully Qualified Domain Name (FQDN) from a
Windows NT computer, you may receive the following error message:
   System error 53 has occurred. The network path was not found.
NOTE: You may also receive this error if you misspell the name of the
remote computer.
When you attempt to establish a NetBIOS over TCP/IP connection (such as a
file share or print share) to a remote computer, your computer must:
 - Locate the IP address for the remote computer.
 - Establish a TCP/IP connection to the remote computer.
 - Establish a NetBIOS session to one of the NetBIOS names registered on
   the remote computer.
Windows NT 4.0 computers use the following logic when using a FQDN for this
process: (for example, when you type "net use \\\public")
 - Use a DNS or hosts file to locate the IP address for
 - Establish a TCP/IP connection to that IP address.
 - Try to establish a NetBIOS session to the NetBIOS name "host1".
 - If that fails, send an Adapter Status Query to the IP address, and parse
   the returned NetBIOS name table for the server name.
 - Establish a NetBIOS session to the server name.
For cases when the hostname does not match the NetBIOS (server) name, this
process relies upon the Adapter Status Query, which is a UDP datagram sent
to UDP port 137. In some cases, such as certain firewall environments, the
Adapter Status Query may fail.
To resolve this problem, obtain the following fix or wait for the next
Windows NT service pack.
This fix should have the following time stamp:
   10/22/97  12:25p  263,824 Rdr.sys  (i386)
   10/22/97  12:22p  510,352 Rdr.sys  (alpha)
An updated version of Rdr.sys offers a new registry parameter to slightly
change the above logic:
 - Use a DNS or hosts file to locate the IP address for
 - Establish a TCP/IP connection to that IP address.
 - Try to establish a NetBIOS session to the NetBIOS name "host1".
 - If that fails, try to establish a NetBIOS session to the NetBIOS name
   "*SMBSERVER      ".
Please see the following article in the Microsoft Knowledge Base for more
information on the *SMBSERVER name and why it is registered on Windows NT
   ARTICLE-ID: Q161431
   TITLE     : Connecting to NetBIOS Resources Using DNS Names or IP
The new registry parameter that allows control of this behavior is:
   Value: FqdnUsesSmbServerName
   Key: HKLM\CurrentControlSet\Services\Rdr\Parameters
   Value Type: REG_DWORD - Boolean
   Valid Range: 0,1 (False,True)
   Default: 0 (False)
   Description: Setting this parameter to "1" causes your computer to try a
                NetBIOS session to the name "*SMBSERVER      " instead of
                using an Adapter Status Query when the hostname part of a
                FQDN does not match the NetBIOS computername on the target
NOTE: Service Pack 3 must be applied to Windows NT 4.0 prior to applying
this fix.


Author Comment

ID: 1571705
Thanks alot. I figured it out from what you said. The domain name was just set incorrectly, stupid mistake A. Well sometimes it is the simplest thing, but thanks for making my brain look in the right place.

Featured Post

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

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

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
An article on effective troubleshooting
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

830 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