| Author |
Message |
pete horm
Guest
|
 Posted:
Thu Dec 30, 2004 1:31 am Post subject:
Strange problem with WINS |
|
|
Hi Everyone,
I have a strange problem with a grading software program. It prompts you
for an IP address of the grading server when opened. Here is the strange
part. If the client has the DHCP server dole out the WINS server
addresses, I type the address 10.10.10.10:123 it takes 20 to 30 seconds to
get the prompt for a login, and it works fine until I close it and it takes
a long time to close. If I put the WINS servers directly into the TCP/IP
settings of the client, and type the same address 10.10.10.10:123 the
username and password prompt pop up almost instantaneously. Now what is
strange is that if I type in the name of the server like this:
servername:123 on those slow clients it opens up instantaneously. Does
anybody have any ideas? One other note is when I use the nbtstat -A
10.10.10.10 for that server's IP address I get "Host not found". When I
used nbtstat -a servername, I get a response immediately. I don't know if
that has anything to do with it or not. I have successfully released and
refreshed that server with the WINS server. Thanks in advance for any
suggestions.
pete |
|
| Back to top |
|
 |
Herb Martin
Guest
|
| Posted:
Thu Dec 30, 2004 6:06 am Post subject:
Re: Strange problem with WINS |
|
|
"pete horm" <pasahorm4@fastmail.fm> wrote in message
news:1walcxtgud6z3$.1342uktrc0uj8$.dlg@40tude.net...
| Quote: | Hi Everyone,
I have a strange problem with a grading software program. It prompts you
for an IP address of the grading server when opened. Here is the strange
part. If the client has the DHCP server dole out the WINS server
addresses, I type the address 10.10.10.10:123 it takes 20 to 30 seconds to
get the prompt for a login, and it works fine until I close it and it
takes
a long time to close. If I put the WINS servers directly into the TCP/IP
settings of the client, and type the same address 10.10.10.10:123 the
username and password prompt pop up almost instantaneously.
|
Did you remember to give the DHCP server BOTH the
WINS server address and the NODE TYPE?
When assigning WINS servers, DHCP is (practically)
required to assign the NODE TYPE too.
Normally: 0x08 or H-TYPE is the correct setting for
most netowrkn.
| Quote: | Now what is
strange is that if I type in the name of the server like this:
servername:123 on those slow clients it opens up instantaneously. Does
anybody have any ideas? One other note is when I use the nbtstat -A
10.10.10.10 for that server's IP address I get "Host not found". When I
used nbtstat -a servername, I get a response immediately. I don't know if
that has anything to do with it or not. I have successfully released and
refreshed that server with the WINS server. Thanks in advance for any
suggestions.
|
--
Herb Martin
|
|
| Back to top |
|
|
pete horm
Guest
|
| Posted:
Thu Dec 30, 2004 6:13 pm Post subject:
Re: Strange problem with WINS |
|
|
Hi Herb,
thanks for your response. I do have it set to -H 0x8 in DHCP, which I
think queries names servers first, then looks by broadcast.
pete |
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Thu Dec 30, 2004 10:36 pm Post subject:
Re: Strange problem with WINS |
|
|
"pete horm" <pasahorm4@fastmail.fm> wrote in message
news:ylro9ijiex03.102c5c5ekappz$.dlg@40tude.net...
| Quote: | Hi Herb,
thanks for your response. I do have it set to -H 0x8 in DHCP,
|
Well durn, that would have been an easy explanation
for different behavior between DHCP and manual
assignment.
| Quote: | which I think queries names servers first, then looks by broadcast.
|
That is correct, it's called hybrid or H-node.
04 reverses this (mixed or m-node resolution) and there are
GOOD reasons for using it in a small number of very large
wide-area networks.
MS machines default to h-node if you set them manually
and have no defaut if you use DHCP so it seems likely
this would be your difference.
Try "IPconfig /all" under both conditions (when it works
well and when it is slow). For WINS servers and Node
Type if they are the same there should be no difference
in NetBIOS resolution behavior.
If they still is, then we must be dealing with a fail over
to DNS or a straight DNS resolution difference.
--
Herb Martin
> pete |
|
| Back to top |
|
|
pete horm
Guest
|
| Posted:
Tue Jan 04, 2005 12:05 am Post subject:
Re: Strange problem with WINS |
|
|
Hello Herb,
Thank you for your help. Last year we were still using WINS exclusively.
Now that we have some XP machines, and a couple of new servers, I added
DNS. That is what is making the login for this program so slow. If I
don't have DNS servers listed, it opens right up. It must be trying to use
DNS. I even tried a reverse pointer record for the IP, but it still didn't
speed things up. I can get immediate access by using the Netbios
name:port, or DNS name:port. So it looks like a trip to a bunch of
machines to change the server settings in the software. Thanks again for
your help.
pete |
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Tue Jan 04, 2005 8:30 am Post subject:
Re: Strange problem with WINS |
|
|
"pete horm" <pasahorm4@fastmail.fm> wrote in message
news:1m6hxy2rr0a2k$.1ob7rroq6u48.dlg@40tude.net...
| Quote: | Hello Herb,
Thank you for your help. Last year we were still using WINS exclusively.
Now that we have some XP machines, and a couple of new servers, I added
DNS. That is what is making the login for this program so slow.
|
Well, not exactly. DNS won't 'do that'-- wrong DNS will.
| Quote: | If I
don't have DNS servers listed, it opens right up. It must be trying to use
DNS. I even tried a reverse pointer record for the IP, but it still
didn't
speed things up.
|
Reverse (i.e., PTR) records are practically irrelevant
but it does indicate that you may be flailing a bit.
| Quote: | I can get immediate access by using the Netbios
name:port, or DNS name:port. So it looks like a trip to a bunch of
machines to change the server settings in the software. Thanks again for
your help.
|
First I would solve the problem.
Are all of your CLIENT machines using STRICTLY
the Internal DNS server (set)?
Is the Internal DNS server set holding the correct
entries for your network?
Specifically, are you SERVERS properly setup as
DNS (and WINS) clients in the NIC--> IP properties?
Are multiple servers (in either set) fully replicated?
Do NOT included external DNS servers in the client
settings. -- only internal DNS server can/must be listed.
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
Restart NetLogon on any DC if you change any of the above that
affects a DC and/or use:
nltest /dsregdns /server:DC-ServerNameGoesHere
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
--
Herb Martin
> pete |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in