Solved

Error 53. Computer Name not found using a DOS 6.22 network boot client

Posted on 2004-03-25
12
841 Views
Last Modified: 2007-12-19
Using network monitor I see the NS request from the client. I also see the reply from the server. I queried the MAC address to verify the NICS   I see in the capture.

The weird part is that I used this and other similar floppy disks and it worked in the past. I have turned on auditing. I have run MS Baseline Security Analyzer.

Thoughts, suggestions, help?
0
Comment
Question by:gee_gdavid
  • 5
  • 3
12 Comments
 

Expert Comment

by:CYBERUG
ID: 10680235
I often get this error when having to do a ris install across a cisco router, to address the problem I normaly reduce the 10/100 nic down to 10mb so as to pass smoothly through the cisco hub or router.
If you have a config disk for the nic yous it to reduce to 10mb and reconfigureafter youve completed your install. (or leave at 10mb)(?).
0
 
LVL 4

Expert Comment

by:lstonge
ID: 10683341
Where do you get this problem? If it's when mapping a drive, just be sure the name of the server and the name of the share do not exceed 13 characters and contain no special characters or spaces. Also, you can't map drives with ip instead of name in dos, like \\192.168.0.x\sharename.

Give more info please. I often use network boot floppies to ghost computers to and from servers, for example, but there are many thing to consider, like the server o/s, the kind of link you want, the nic, etc.

If you have the same boot disk that was working before and it uses tcpip, do you try to map drives on a xp or 2003 computer? Then you would have to adjust some things, like disabling SMB signing in windows.

Luc
0
 

Author Comment

by:gee_gdavid
ID: 10683584
Here is some additional background.

The UNC is unchanged. For the last six months this UNC (server and share name) have not changed. The bootable floppies have not changed. The network infrastructure has not changed (no routers, using a switch). The change that was introduced was Windows update and the Microsoft Baseline Security Analyzer.

As I mentioned in the initial post, the client sends an NS request. The server responds to the request. The client sends the request one time only. The next traffic from the client is an ARP request to the gateway. At that point all traffic ceases and the client posts the Error 53.  The same client floppy can connect to a share on a Windows 2000 server.

I am suspicious of the anonymous settings on the 2003 server which I reversed to the high risk setting. The server was rebooted but the change was unproductive.

More ideas?
0
 
LVL 4

Expert Comment

by:lstonge
ID: 10683734
The SMB signing is required by default on 2003 server. It is enabled but not required on 2000 server. It is not supported on DOS or win9x.

Check:

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\

REG_DWORD: RequireSecuritySignature=0 (default=1)

Luc
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:gee_gdavid
ID: 10740841
Sadly, the SMB parameter is set to 0.

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\

REG_DWORD: RequireSecuritySignature=0 (default=1)


Thus, the problem persists. More ideas?
0
 
LVL 4

Expert Comment

by:lstonge
ID: 10770122
Try to force "enable netbios" in tcpip properties (under wins tab).

Luc
0
 

Author Comment

by:gee_gdavid
ID: 10782803
Here is an update. I looked more closely at the network capture and found, in the NS reply that it includes two references. Remember that the source computer (Win 2003 Server) has two adapters on separate networks. 192.168.0.x and 192.168.100.x. The subnet is 255.255.255.0.  The order of the name references lists the "remote" network first. This is why I see traffic pointing to the gateway. Hmmm.  Two questions:
Why would the client work for months and now fail? Why would the server offer a single reply with two resolutions?

Ooops, a more important question: How do I fix this?

DW
0
 
LVL 4

Accepted Solution

by:
lstonge earned 500 total points
ID: 10786835
Try to use the lmhosts file on the client to resolve the name locally.

content for lmhosts file:

<ip-of-server> <server-netbios-name> #PRE #DOM:<domain-netbios-name>

(Don't include the <>)


Check also this key on the 2003 server:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RemoteAccess\Policy\Allow LM Authentication

It should be 1, change it if it is 0

This key can be changed be IAS or RRAS security.

http://support.microsoft.com/default.aspx?scid=kb;en-us;826157&Product=winsvr2003

I'm checking for the resolution problem but didn't find anything yet. But if you use the lmhosts file, it will bypass this problem for now.

Luc
0
 
LVL 4

Expert Comment

by:lstonge
ID: 10786856
BTW ms-dos is not mentionned in this q826157 but it applies to it also.

Luc
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Cisco 2800 Enable PRI Controller 1 35
VIRL IP adress 3 58
DNS Redirection 6 27
Cannot browse to favorite website apologeticspress.org but friends can 20 33
This is an article about my experiences with remote access to my clients (so that I may serve them) and eventually to my home office system via Radmin Remote Control. I have been using remote access for over 10 years and have been improving my metho…
Resolve DNS query failed errors for Exchange
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

867 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now