Solved

Multi homed NT Server in Domain - Slow access to workgroup. Why?

Posted on 1997-03-11
5
242 Views
Last Modified: 2013-12-19
I have an NT server with two network cards in it. One is attached to an NT domain of which it is a member (Just a server, not a PDC or BDC). The other card is attached to a workgroup. I am using TCP/IP only. Ping works fine to all machines in the domain and to all machines in the workgroup. There are no pauses or problems with ping when i use the ip address or the ip name. I am not running a WINS server anywhere but am using lmhosts.

The problem: When I do a "net use z: \\booth1\share", where booth1 is a machine in the workgroup, it locks up for around 50 seconds before the command is successful. Simlarly, if I browse the workgroup using "network neighbourhood", the list of machines in the workgroup (about 10) comes up in a few sconds but if I then click on one to view the shares, another 50 second gap occurs.

I ran the network monitor and got the following results. When a "net use ..." is performed on the server to a client in the workgroup, there is an immediate name query from the server which is answered straight away by the client. Some more stuff takes place within a second (a session request by the server and a positive session response by the client). Then there is a 50 second gap with a couple
of TCP packets going from server to client. After the huge pause, the server sends a C negociate message with a list of dialects (of LAN Manager?) in it. Immediatly, the client replies (it picks number 7) and everything then works.

How do I get it so that access to the workgroup machines do not have this 50 second pause? I need to keep access to the domain as well, of course.
0
Comment
Question by:garyw
  • 3
  • 2
5 Comments
 

Accepted Solution

by:
drodrigu earned 200 total points
ID: 1559267
One solution (There is not the best) is that the workgroup name
be the same of Domain Name. And in the lmhosts of each machine put the ip addr ess of the PDC like:
ip    "domain_name       \0X1b" #PRE      -The domain name
The "   " must have exactly 15 bytes length.

your  can check this by typing nbtsat -c in the command prompt
and see the line:     domainame  <1B>  UNIQUE    IPADRESS


ip     name_server       #PRE #DOM:domain_name
..For all PDC or BDC


The best solution is to use a WINS Server
0
 

Author Comment

by:garyw
ID: 1559268
I am happy to put in a WINS server but why would this help?

As I understand it, WINS maps machine names to ip addresses. If I ping a machine in the workgroup (e.g. ping booth1) from the server in the domain (the one with the 2 network cards), it works straight away. If the problem was WINS, wouldn't this take 50 seconds as well?

0
 

Expert Comment

by:drodrigu
ID: 1559269
With the WINS Server you acelerate the Browsing process, because each machine instead of broadcast to search al machines it directly ask to the wins server for all the workgroups,
machines and shares.

IF there is no problem with your plans, and your have only
one workgroup try to put this the same name as the domain, this will help you because the PDC is the master browser. And only put in the lmhosts. the lines I say you in the proposed answer from me.
0
 

Expert Comment

by:drodrigu
ID: 1559270
With the WINS Server you acelerate the Browsing process, because each machine instead of broadcast to search al machines it directly ask to the wins server for all the workgroups,
machines and shares.

IF there is no problem with your plans, and your have only
one workgroup try to put this the same name as the domain, this will help you because the PDC is the master browser. And only put in the lmhosts. the lines I say you in the proposed answer from me.
0
 

Author Comment

by:garyw
ID: 1559271
I will move the booth1 machine from the existing workgroup to a workgroup with the same name as the domain and edit it's lmhosts as you suggest.

I will then go to a server on the domain and do a "net use z: \\booth1\temp" and the 50 second delay should be gone? It will take a day or so as the system is in heavy use at the moment (despite the bad network delays)
0

Featured Post

Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

Question has a verified solution.

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

Suggested Solutions

Are you one of those front-line IT Service Desk staff fielding calls, replying to emails, all-the-while working to resolve end-user technological nightmares? I am! That's why I have put together this brief overview of tools and techniques I use in o…
An article on effective troubleshooting
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

820 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