?
Solved

Why are my DOS machines not finding the server?

Posted on 2011-10-06
8
Medium Priority
?
443 Views
Last Modified: 2012-05-12
I have 3 DOS machines that used to be able to communicate with a Windows NT Server VM but won't now. I have several Wireshark captures of attempts at filesharing, both successful (in the past) and failed (of late).

I also have the original physical Windows NT server that the VM is supposed to replace. The physical server is still working for some reason. I've attached a Wireshark capture of failed attempt at requesting files from the VM and then a successful attempt to get files from the physical server.

IMPORTANT NOTE - To access the Wireshark capture file, rename the zipped file to remove the .txt extension and leave the file ending with .pcap
diserver3-fail-and-diserver2-suc.zip

All of the machines involved are part of a Presstek press laser imaging system. There are 3 DOS machines that control several lasers apiece, a Windows NT Server that stores the data to be imaged, and a Windows 95 VM that coordinates the imaging process.

I'm trying to replace the original Windows NT data server with a similar VM. The DOS machines can't seem to communicate with the NT Server VM anymore.

DOS Machine 1: ICU_1 or Intel-Hf_5c:9d:b3
DOS Machine 2: ICU_2 or Intel-Hf_5c:80:1d
DOS Machine 3: ICU_3 or Intel-Hf_5c:80:a0
Windows NT Server (Physical): DI_SERVER2 or 192.168.172.179 or Adaptec_1A:78:f0
Windows NT Server (VirtualBox VM): DI-SERVER3 or 192.168.172.110 or CadmusCo_f9:6a:4c
Windows 95 (VMware VM): Prism_VM or 192.168.172.113 or Vmware_96:7b:50

The problem looks to me like the DOS machines cannot resolve the name of the NT Server VM (packets 461-566). I don't know how to fix that. I've tried all I can think of and google. I have no idea what might have changed in our environment that might caused this.

The capture included shows the Prism_VM telling the DOS machines to start imaging from DI-Server3 (VM). The DOS machines edit some log files on Prism_VM, and then try to find DI-Server 3. They fail name resolution, give up, and write the failure to the logs on Prism_VM. At this point I restart the imaging process using the physical data server instead (DI_server2). The process starts all over again and instead of failing name resolution the capture ends in the middle of the DOS machines happily requesting and receiving data from the physical data server.
0
Comment
Question by:KaiserGuy
  • 5
  • 3
8 Comments
 
LVL 43

Expert Comment

by:Steve Knight
ID: 36925383
cant look at the captures from here but could this be a wins issue perhaps you arent giving out wins through dhcp any more or fixed wins settings pointing to wrong place?

Will look at cap later if i can.

Could also try forcing using lmhosts files if needed i suppose.

Steve
0
 

Author Comment

by:KaiserGuy
ID: 36925453
I tried configuring lmhost on one of the DOS machines but it did not seem to work. I suspect I put file in wrong place. I did not find a pre-existing lmhost file.

DHCP is currently being handled by a WRT54GS v4.71.1 router. I have installed DHCP on our Server 2008 R2 servers in the past but struggled to be certain I was configuring them properly. I eventually gave up and used the router because it is so simple to configure. This means there is now WINS setting to configure.
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 36925521
hmm, cant remember lmhosts location on win9x, been a long while but should be searchable on c drive. Make sure hasnt got .txt on the end too and needs very specific format.

Without wins things may be more difficult.  would suggest manually setting wins server to nt4 server in properties advanced section on each workstation and seerver nic then checking on server wins console that they are all registered in there.

Steve
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 43

Expert Comment

by:Steve Knight
ID: 36925535
if using router for dhcp for other windows clients watch that it is giving out your internal dns servers if running a win 2000 or above domain btw.
0
 

Author Comment

by:KaiserGuy
ID: 36925568
Our two internal DNS server are 192.168.172.1 and 192.168.172.176 as configure in respective order in the router. I believe BTP-AD (192.168.172.1) is involved in the Wireshark capture.
0
 
LVL 43

Accepted Solution

by:
Steve Knight earned 2000 total points
ID: 36925638
win 9x wont use dns for name resolution except for ip comms rather than windows access so please look at putting wins settings on those boxes and think it will see each other then.
0
 

Author Closing Comment

by:KaiserGuy
ID: 36950183
http://technet.microsoft.com/en-us/library/cc750589.aspx
Used section titled "Enabling WINS Lookups"

Basically enabled WINS resolution for our domain in the DNS manager and specified a WINS server IP
0
 
LVL 43

Expert Comment

by:Steve Knight
ID: 36952479
Interesting.  I know of that when we are talking new clients such as 2000/XP onwards talking back to old OS's as the old ones will register in WINS and the new ones can then query WINS through DNS effectively.

What I thought was the case for you was old clients talking to old serverd and therefore each client would need a WINS server address in ip config, and a WINS server running on (any) one of your boxes there for them all to register with.

Anyway at least you are working by the sounds of it.... and nice link there.  Hadn't seen that one though had implemented this with a customer before.

Steve
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

I will assume you are running a non-server version of some sort of Windows throughout this article. There are many flavors of Windows since Windows Server 2000 - 2008, XP Home & Pro, Vista Home & Pro, and Windows 7 Starter, Home, Pro, Ultimate, etc.…
I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
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…
Suggested Courses
Course of the Month14 days, 20 hours left to enroll

840 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