serving client subnets on your L3 switches/routers.
-Original Message-
From: Kent Hundley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 26 September 2001 10:18 a.m.
To: [EMAIL PROTECTED]
Subject: RE: NT Users cannot logon [7:21130]
Sounds like a name resolution issue. (Netbios name resolution
ECTED]
Subject: RE: NT Users cannot logon [7:21130]
this syntax is for the lmhosts file, instead of the hosts file. the hosts
file is just like in unix, a local static mapping of hostnames to ip
addresses so the domain info doesn't apply. lmhosts is what you want to
give a windows machine a local
llers, domains etc...
on my w2k system it's located in c:\winnt\system32\drivers\etc
dave h
-Original Message-
From: Ole Drews Jensen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 26, 2001 3:08 PM
To: [EMAIL PROTECTED]
Subject: RE: NT Users cannot logon [7:21130]
More...
More...
If you can ping a server by its IP address but not its name, try to add it
in the workstations hosts file.
The hosts file is in C:\windows on 95 an 98 computers, but I can't remember
where it is on NT/2000 computers. It might not even be there, so search for
hosts.sam which is a sample f
Try this:
1) Can you ping server on subnet A by it's name from a workstation on subnet
B?
Example: ping acct_svr_1
2) Do you have any access lists on the router?
If you do, try to disable them
3) Can you from the workstation click Start -> Find and find the server by
its IP ad
Sounds like a name resolution issue. (Netbios name resolution, not DNS) Do
you have a WINS server? You typically will need a WINS server for Netbios
name resolution across subnets. (and hence logon capability)
HTH,
Kent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTE
Do you have WINS server setting configured correctly for
the client workstations.
Unless u have a domain controller, clients will not know how
to contact the domain controller... WINS helps you on that.
Paul
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=21134&t=21130
---
7 matches
Mail list logo
