my Clients won't login w/out reboot occassionally after NT4/to Win2k?

[KB]

I've got an annoying problem that has appeared since I changed (not
upgraded - wiped and reinstalled) a server from NT4 to Windows 2k.

Prior environment was a Win 4 SP6a server, running wins for a +/- 300
client win98 workstation lan. Despite having 2 subnets all clients
could see the wins server (ya, weird but it worked, don't ask me).

After wiping the server and installing Win2K Server SP4, active
directory, wins, dns (dns not being used by the win98 clients) of
course I could not use wins from the extra subnet (had to load lmhosts
on each machine) - many clients on a random basis will not login
without a reboot. After reboots client logs in fine, perhaps many
times without issue.

No other adjustments were made other than the server. Affected
clients falls into either subnet. Reloading a test machine, no
change. Removing the wins resolutions and using only lmhosts has no
effect.

Any ideas

 

[Herb Martin]

I've got an annoying problem that has appeared since I changed (not
upgraded - wiped and reinstalled) a server from NT4 to Windows 2k.

So, you are pretty confident in the hardware
and wiring and everything else is an unknown?

Did you remember to make the SERVER(s) WINS
clients?

Prior environment was a Win 4 SP6a server, running wins for a +/- 300
client win98 workstation lan. Despite having 2 subnets all clients
could see the wins server (ya, weird but it worked, don't ask me).

What's weird about it? That is the way it SHOULD work.

WINS clients use (routable) IP to register and resolve
names from WINS server so they can be anywhere on
your routed network.

After wiping the server and installing Win2K Server SP4, active
directory, wins, dns (dns not being used by the win98 clients) of
course

It should be -- it isn't as essential but it may help them.

I could not use wins from the extra subnet (had to load lmhosts
on each machine) - many clients on a random basis will not login
without a reboot. After reboots client logs in fine, perhaps many
times without issue.

Can you ping (by name or just number)? Does routing work?

Can you resolve any names?

No other adjustments were made other than the server. Affected
clients falls into either subnet. Reloading a test machine, no
change. Removing the wins resolutions and using only lmhosts has no
effect.

You aren't really describing your problems but just
saying it doesn't work, or you re-install without giving
us the EXACT symptoms, preferably with error messages,
and the results of the simple and standard tests like:

ping NAME

ping IP_ADDRESS

net use \\ServerName

net use \\ServerName.Domain.com

net use \\Server_IP_Address

nslookup ServerName

etc.

 

[KB]

So, you are pretty confident in the hardware
and wiring and everything else is an unknown?

Yes, nothing has changed.

Did you remember to make the SERVER(s) WINS
clients?

Please explain more, I don't understand the question.

What's weird about it? That is the way it SHOULD work.

It was always my understanding that WINS would not route, and it was
required to have a wins server for each subnet.

WINS clients use (routable) IP to register and resolve
names from WINS server so they can be anywhere on
your routed network.


It should be -- it isn't as essential but it may help them.



Can you ping (by name or just number)? Does routing work?

Can you resolve any names?

no name resolution at all to the pdc. So of course, the lmhosts entry
solved the issue.

You aren't really describing your problems but just
saying it doesn't work, or you re-install without giving
us the EXACT symptoms, preferably with error messages,
and the results of the simple and standard tests like:

ping NAME

ping IP_ADDRESS

net use \\ServerName

net use \\ServerName.Domain.com

net use \\Server_IP_Address

nslookup ServerName

etc.

I'm unable to ping or anything like that as we don't allow default
logins (its an ed environment - must enforce internet policy), users
must authenticate to the domain.

The only errors to report is the generic win98 unable to find server
error (though I'm not 100% confident of that, I'll have to check).

 

[Herb Martin]

Please explain more, I don't understand the question.

You indicated you had a WINS server but it wasn't
performing correctly so you tried LMhosts; and you
need one of them (at least) and LMHosts is not a
very practicaly solution.

You need WINS etc. because you have IP on more
than one subnet with a Microsoft network.

You reinstalled your SERVER - -many people forget
that the SERVERS (even the WINS server) must be
a WINS CLIENT for it to register itself so that the
other machines can find the servers, or they can
find each other for Browse list distribution and such.

NIC->IP->Advance->WINS tab: Make all machines
WINS clients of the WINS server.

It was always my understanding that WINS would not route, and it was
required to have a wins server for each subnet.

WINS does NOT "router" but the clients register with
the WINS server and resolve names using IP which is
ROUTABLE.

WINS just sits there and accepts those registrations
and responds to queries.

no name resolution at all to the pdc. So of course, the lmhosts entry
solved the issue.

If you are happy it can be made to work but it is
much more work if you want Browsing and other
stuff to be really easy.

WINS is easy and just works -- it was DESIGNED
for routed IP-Microsoft networks.

WINS is (ALMOST) irrelevant without multiple
IP subnets.

I'm unable to ping or anything like that as we don't allow default
logins (its an ed environment - must enforce internet policy), users
must authenticate to the domain.

Again you were not specific: can't even ping by IP?

How about the net commands?

Which work? Which fail? What errors?

The only errors to report is the generic win98 unable to find server
error (though I'm not 100% confident of that, I'll have to check).

Well, you want to be more specific than that and
stop using GUI tools to troubleshoot such problem.

Can you ping by IP?