Discussion Locked

Cannot see/logon to network domain

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello fello members

After unsuccessfully attempting to sort this out myself, I have been forced to ask for help. My predicament is I am unable to see or logon to a network domain.

System/configuration:
Windows 2000 professional
Network cardXircom Ethernet II (PCMCIA)
Client:
Client for Microsoft Networks

Service:
File and Printer Sharing for M'soft networks

Protocols:
NWLink NetBIOS
NwLink IPX/SPX
NetBUI
TCP/IP

I do not have any entries in the host/lmhost file, set to automatically determine IP address and have default settings for DNS and WINS. Am able to ping DHCP, WINS, DNS and default gateway in addition to other computers on network.

Cannot however see rest of network in network neighbourhood. Network wizard does not see/allow me to logon onto network domain. Network properties also does not allow me to change from workgroup to domain as does not see domain.

Have also unchecked all protocols except TCP/IP, set default gateway, set DNS/WINS servers, all with no effect.

This I'm sure is something stupid I've overlooked, but because I am at a dead end I am offering 500 points for a solution.

Please help!
Desperate member

13 replies

by howardhenderson

Hi Nev,

It sounds like you are pretty knowledgeable about networks and it has always seemed to me that the tougher the detective chase, the larger the number of 'small probabality' solutions there tend to be.

But based on what you said, successful pinging rules out 'low level' connectivity. It sounds to me like that name resolution is where the problem lies.

The login domain controller is in the local subnet, isn't it? Can you ping it? If so, I'd try 'jump starting' the problem PC by placing an entry in the 'hosts' file (lmhosts if the domain controller is on a remote subnet - with NT 4.0, a person had to reboot after an lmhosts entry to make it 'take' - I'm not sure about Win2K).

After that, do a 'find computer' and see what you can see. If you can see the controller, try joining the domain. BTW, I'm sure you are trying that with appropriate admin rights, aren't you?

You didn't mention how many PC's are successfully served by your WINS and/or DNS services... Are you sure they are operational with other PC's?

Also, I had a problem one time with a Win2K PC that was giving the same trouble you have described - I don't remember all the details - but I know I finally changed the network ID name on it and rebooted and it finally saw the domain and let me use the admin account to create a machine account for the PC on the server...

How much of your WINS/DNS, login controller services are coming from beyond the default gateway? I've had to play with the routing tables on some of my NT 4.0WS PC's, so that they can successfully obtain services from remote subnets (especially when the users at the local PC's also dial out with their local modem onto the Internet).

Hope any of this helps,
Howard H.

by aspasa

hi,

try changing to a 'workgroup name' on your pc to the same name as the domain you wish to see/logon to.

does it see it now?

by aspasa

hi,

try changing to a 'workgroup name' on your pc to the same name as the domain you wish to see/logon to.

does it see it now?

by golovast

Is this one workstation or your entire shop? I've had a similar problems on my network after I upgraded to 2000. Turns out that if you use a different domain name in 2000, it will give you pretty serious problems. Also, did you try pinging your servers by name to check if the client can resolve them?

by nev

Answers:
- One workstation
- Yes have added server and domain entries in host and lmhost file and can ping servers by name.

by stillatit

These are some other longshot possibilities:
1. Check the binding of NetBeui. Make sure it is bound to Client for Microsoft.
2. Make sure Netbuei over TCP/IP is enabled.
3. Try putting in an LMHOSTS file, with an entry for the domain controller,with #PRE and #DOM: tags.
4. If you look in Network Neighborhood under 'Entire Network' do more stations show up? If not, silly as it sounds, check the WINS address in your TCP/IP setup. You should be getting your WINS address from DHCP, and you should be getting a node type as well. If you have any manual entry in the WINS address fields, DHCP will not override them.
5. W2K wants a 15-character computer name. You did not, by chance, force a shorter one or put illegal characters in it?

Good luck.

by kt

Well, it's not quite clear to me if your workstation is on different subnet from you domain controller. If subnet is the same -- sorry, I ran out of ideas. However, if subnets are different, make sure that you have lmhosts file on the domain controller set up with an entry for your workstation. It has to be both ways -- doing it on one end won't help. Good thing to do is to check if you can see the workstation in a network neighborhood on the server.

After making changes in lmhosts file on any machine, you have to either reboot, or run the command "nbtstat -R" (R must be capital) -- it will purge and reload locl NetBIOS cache. This is true for both NT and Win2K.

Of course, lmhosts file is only needed if you don't have WINS server on yor network, or something is wrong with it's configuration (most probably on client side). One thing you can be sure about -- this problem is definitely related to NetBIOS name resolution, which is done by WINS or lmhosts files.

This discussion is closed to new replies.