asked on

Windows 95 cannot verfiy a NT domain

I have recently setup a Windows nT server on a small ethernet network. I setup the NT server 4.0 (service pack 3.0) as the primary domain controller
. The server is running TCPip and Netbeui and the same with the workstations (windows 95). The network services running include computer browser, microsoft Internet information server, netbios interface, network monitor agent
RAS, rip for internet protocal, RPC configuration, server and workstation. The windows 95 workstations are configured to login to the windows NT server domain. But everytime
I try to get the workstations to login I get a message that reads that there is no domain availible to verfiy a login. I am completely confused .. I have tried everything. I can however see the NT server
via network neighborhood but I can only browse directorys set for public view. I can not however login to the server. Can anyone assist me .. I have reload the nt server numerous times and making sure that
I set the PDC. I also can see the workstations from the server via netbeui. Any assistance would be greatly appreciated. I again am running NT4.0 with the service pak 3.0 installed.

bbao

Are you sure you have both NetBEUI on NT server and clients? If so, you should see PDC from Network Neighborhood.

You don't have DHCP server on your PDC, so the client should be manually setup proper IP address to connect them together, are you sure that all the IP addresses at server and client sides are in same network? Or, in other word, do the mask settings are same? If they are no same, you won't connect PDC via TCP/IP.

Please check and let me know how it goes.

Good luck,

jdbrooks

ASKER

I am not running DHCP on the server and TCPIP is configured amongst the workstations and the server. The IP address are one off from each other and all have the same subnet mask (255.155.155.148). On the workstations however I can see the primary domain and even enter the domain and view the public directories on the server. I can not however map drives or even login to the server. My domain name for my server in the TCPIP DNS is however the same as the PDC is this correct.

jdbrooks

ASKER

Adjusted points to 220

woodsmj

Why is the subnet Mask 255.155.155.148???? Please explain the need for this unusual subnet mask-- it may be the problem. First try to see if you can ping the server from a command prompt by IP address and then by HostName. If the net settings were correct, all shares should be seen from all clients, you just wouldn't see the contents of those shares if you weren't logged into the domain and if the permissions for Read were not set to "Everyone". Is there any chance, these machines are separated by
a router? Any chance a netbios scope ID has been set on any of the workstations?

mzito

I would say that it is likely the subnet mask is your problem. That's the subnet mask for a mixed class A network.... if it is a small network (i.e. less than 254 workstations), etiquette dictates you should use a class C network space, and ideally the private network space- 192.168.x.x where the subnet mask would be 255.255.255.0. It is not good form to use a class A-size network if you don't need it. No real reason, but in this case, this very odd subnet mask is likely your problem. If you'd like more clarification, feel free to email me @ mzito@wwprsd.mercernet.net.

Best Wishes,
Matthew Zito

mpopal

Like the others say, the subnet mask 255.155.155.148 could be your problem. I think it's definitely your problem. 155s and 148s are not even valid subnet mask values. You need to fix your subnet first, second make sure your not running the WINS service if your only dealing with one subnet.

ASKER CERTIFIED SOLUTION

Heiko Bialozyt

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mpopal

heiko,

As I said earler, 255.155.155.148 is not a valid subnet. Open up a TCP/IP book and see for yourself. Only 192, 224, 240, 248, 252, 254, and 255 are valid.

RobertB

I think subnet mask is not the problem. Try first to remove TCP/IP protocol from your workstation and use only NetBeui.
Then try to remove workstation from list of computer in the domain (server manager utility), wait for a while (15 min) and to re-add it with the same (or then another) name.