|
|
| trebor 2001-05-13, 9:52 am |
| OK here I go again. I realize I should be able to do with my eyes closed namely making a simple client/server tcp/ip network but I am still having problems that I am sure someone here can help me with.
I have a Windows 2000 Advanced Server running DNS and DHCP (at least I have installed DNS and DHCP) it is also the domain controler.
My "clients", all Win 98 machines give me an error message when they log on "no domain controller found" (my clients are running a German version of Windows so I don't know exactly what the error message is in English, but in any case they can't find the Domain Controler.) But then they can see the shares on the DC by using the "Find Computer..." but not in Nework Neighborhood.
I can ping the DC from the client with the server name and with the IP address I have assigned to it (10.10.0.1)
Oh, by the way, yes I created a scope and activated it and yes I authorized the DHCP server.
Any ideas?
Trebor | |
| Yeti-GBR1 2001-05-13, 2:13 pm |
| Ok is it in native mode or mixed? | |
| trebor 2001-05-13, 11:25 pm |
| Although for the life of me I can't think of how that would affect my problem, it is in mixed mode. I only have the one Win 2000 server so I can change that if I want.
Trebor | |
| Yeti-GBR1 2001-05-14, 3:47 am |
| I was just making sure thats all, I have seen it where in Native mode the same thing happens. Right thats ruled out then.
1.Is there anything in the DC event logs at all, errors or warnings?
2.Ok you can ping the DC, have you tried using a net use to connect from a DOS command line on the W98 PC's?
3.Try installing WINS on the DC (yes I know its CPU intensive) but it may help.
4.I'll think of somemore in a little while 
Yeti the Confussed  | |
| trebor 2001-05-14, 5:20 am |
| I will going to try the net use on the Win 98 machine toda y I will let you know what happens. I have never done that.
My network works fine when I install NETBEUI protocol but I wanted to experiment with a pure TCP/IP environment so don't you think making a WINS server might be cheating.
I will let you know about the events log after I boot up Server (a trial in itself with only 64 MB RAM). Thanks for your help.
Trebor | |
| dentonb2000 2001-05-14, 5:52 am |
| Possible that the PDC Emulator FSMO is down?
Have you installed the AD Service client on the Windows 98 machines so that they can use NTLMv2?
Can you ping the server by both the netbios name and FQDN?
Do you have any NT or Windows 2000 clients available on the network that you can test with? I would like to see whether they generate the same error. If you have access, even temporarily, add the machine to the domain and see whether or not you get the "Welcome to blah-blah domain" messsage.
Just some questions. | |
| trebor 2001-05-14, 6:20 am |
| Whow Denton. Did I exagerate the size of my network? It is only three machines. And at the for two days I have been wrestling with a misbehaving Monitor driver on one so I have only the use of two machines until I fix that. The server has of course all the FSMO roles and seems to be working fine.
The servers name is gooddog and I can ping gooddog and 10.10.1.1 form the Win 98 client.
But wait what is this about installing AD client on the Win 98 machine? Did you just make that up or have I missed something really important?
Trebor | |
| dentonb2000 2001-05-14, 7:15 am |
| quote:
My "clients", all Win 98 machines give me an error message when they log on "no domain controller found"
This statement doesn't convey how many client machines there are...sorry for the confusion.
As far as the AD client goes, check the Windows 2000 Server cd for the client. I believe it to be in the tools folder. This is a patch that allows the client to use NTLMv2, it includes a fault toerant DFS client and allows the client to change passwords at any DC vice the PDC.
While none of these should affect the logon, it would not hurt to try. | |
| trebor 2001-05-14, 8:57 am |
| I am starting to believe that I should re-install TCP/IP or try a different NIC. I have assigned a static IP address rebooted Winipcfg showed the IP address to be 0.0.0.0. Ar-r-rg!
The Event Viewer showed some replication errors but included, "If this DNS server does not have any DS-integrated peers, then this error
should be ignored. "
Oh, and "net use" showed "no entries"
I'll get back as soon as I :
1)re-install TCP/IP
2)Try a different NIC
3)Do that thing that DENTON suggested
I will let you know how it comes out.
Trebor | |
| freak 2001-05-18, 11:50 am |
| you have a DNS server issue. Check under DNS manager and make sure that the SRV records are in there correctly. Also, make sure DHCP is authorized in AD. | |
| Yeti-GBR1 2001-05-22, 9:40 am |
| Just out of curiosity did you manage to fix your problem? If you did what was the resolution? | |
| trebor 2001-05-22, 12:51 pm |
| Jeez, Yeti I was afraid someone would ask that. I was hoping the forum would forget about my incompitence.
The honest answer is - NO. I think Freak is right and that on my little test network I can't get the DNS server to work. I am actually learning a lot now though about DNS because I am researching what that SRV record is supposed to look like. (Any references are appreciated.)
In the mean time I have I have re-installed Netbeui and the machines can at least see each other.
Trebor | |
|
| I had exactly the same problem on my home network. Similar setup too, 2000DC, 98SE and 2000 Clients.
Same error message from 98 clients, same ability to find shares.
I am using manually assigned ip's, dns server address etc.
I only wish I could remember more clearly how I fixed it......I think(don't quote me or I will deny everything)that I had set the domain name incorrectly on the dns tab of either the tcp/ip properties or the client for microsoft networks properties on the clients.
I have vague memories that I had used the full domain name eg examnotes.com when I should have just used examnotes
I am positive it was a client configuration issue.
I hope you can make some sense out of that, sorry I can't remember what I did more clearly but it was some time ago. | |
| trebor 2001-05-25, 6:03 am |
| That does encourage me Gigas. I am pretty sure that it is a DNS problem too. I feel like such an amature clicking around AD. I wonder if anyone could recommend a website that would explain how I am supposed to configure DNS. I mean all my material is very superficial on the subject.
I am going to start all over again tomorrow configuring DHCP and DNS on the DC. If anyone has a step by step guide let me know.
Trebor (down, but not out) | |
|
| Try http://www.petri.co.il/ref_2153.htm
Very good site in general, has heaps of usefull links.
If you need a break from study the page about his altercation with Transcender is very interesting reading.
I hope you get it sorted out, I know I kicked myself once I spotted the problem, just wish I could be more precise as to what I did. | |
| trebor 2001-05-25, 2:52 pm |
| Don't you think I could generally rule out DNS problems when I can't even ping the server from the host using the IP Address? Nor can I ping the host from the server. The two machines just aren't seeing each other.
I have statically assigned IP addresses so DHCP problems can be ruled out. Ther NIC is OK because like I said using Netbeui everthing is OK.
Trebor | |
| dentonb2000 2001-05-25, 4:54 pm |
| If you can't ping by IP then it is not DNS. How are the machines connected? Hub, cross-over cable? what? | |
| trebor 2001-05-26, 12:16 am |
| Coaxial Cable. | |
| dentonb2000 2001-05-26, 10:01 am |
| correct cables and termination? | |
| trebor 2001-05-26, 12:41 pm |
| Yup.
But in case you are still ready to have patience with me I have gotten a clue from the event viewer on the client machine (I am dual booting the client with 98 and 2000). This is what it says and by the looks of it it could be the problem:
The master browser has received a server announcement from the computer WORKHORSE that believes that it is the master browser for the domain on transport Nbf_{7A7C1BE0-1555-11D5-852A. The master browser is stopping or an election is being forced.
I haven't found any explanation on Technet yet but am still looking. WORKHORSE is is the server's name.
trebor
PS: When I got that message, the client apparently could not reach the server in any way. Not with ping, My Network Places, net view, etc. | |
|
| Trebor, are you still running tcp/ip or have you gone to netbeui exclusively?
The reason I ask is that I am getting conflicting signals from your posts, perhaps a quick run down on your current setup would be of value to us all in helping you (and ourselves)in getting to the bottom of this problem.
Useful info would include.....
protocol(s) in use
If tcp/ip then
tcp/ip addresses
subnet mask
ip addresses /subnet masks of other machines on the network etc.
This would be of benefit in trying to build up a picture of the most likely causes of the problem.
Re your comment below
The master browser has received a server announcement from the computer WORKHORSE that believes that it is the master browser for the domain on transport Nbf_{7A7C1BE0-1555-11D5-852A. The master browser is stopping or an election is being forced.
I have previously posted a basic (but long) explanation of what causes browser elections in answer to someone elses query, it is here....
http://www.examnotes.net/forums/sho...90186#post90186
You go on to say that you can't ping which is why I ask if you are running netbeui exclusively?
Just my 2c worth at this point but I think if we had a clear picture of current settings it would benefit us all
I love a challenge | |
| trebor 2001-05-27, 1:26 pm |
| This is getting embarrassing but since I am the only one with an actual problem to discuss I guess I will continue.
I didn't know that fact about elections. That could still be the problem but I haven't gotten it to work yet.
I have reconfigured the machines so much I forget myself what their configuration "de jour" is. OK here are the facts:
Machine #1 dual booting
Win 98 in a workgroup can communicate using Netbeui no problem
Advanced Server as a DC
IP ADDRESS 10.10.10.2
Subnet mask 255.255.255.0
At the moment I have disabled DNS because I am trying to narrow down the problem
Machine #2 dual booting Win98 in a workgroup with Netbuei no problem
and Win 2000 Professional
using TCP/IP
IPADDRESS 10.10.10.5
subnet mask 255.255.255.0
I tried enabling DHCP (so using APIPA) today and it just keep giving itself an address of 0.0.0.0
I see I have a new "event" in Event Log called a "media disconnect error" and a second one called "DNS caching Resolver is experiencing network performance problems" (could it be a physical problem after all?)
I would like to thank you for your patience and I hope I am not the only one learning something here. But since questions are my specialty I will keep it up until the problem is solved or someone tells me to shut up.
Trebor | |
|
| Shut up. Just kidding,
First off win2k NEEDS DNS !!!
Remember your nt4 studies relating to netbios names? 15 character maximum length with a hidden 16th character which is used to announce services running on the machine?
The services are found via DNS in win2k.
My advice would be to get rid of netpooie altogether.
Give the 98 boxes ip addresses in the 10.10.10.x range.
Set their DNS server to be 10.10.10.2
Get all machines able to ping each other.
Setup DNS from the begining, ie remove what you have and start again.
This could prove controversial but.... Create reverse lookup zone first. Then create forward lookup zone. I know this is not the M$ or (anyone elses) approved method but it works best. 
Make sure you set "allow dynamic updates ?" to "yes"
Make sure there is a host record for the dns server in the forward lookup zone and a pointer record for the same machine in the reverse lookup zone.
Create host records for your other machines, be sure to tick the box that says "update associated pointer record ?"
Then if all has gone well and you can do an nslookup for each machine, both forward and reverse lookup, everything else should just fall into place.
There are links to some very good win2k DNS resources here...
http://www.microsoft.com/australia/...e/examtips5.htm
I want to see you win this one mate.... | |
| trebor 2001-06-07, 4:20 am |
| I know you have all been sitting on the edge of your seats in anticipation whether I would ever get this figured out.
Well, I did. Sort of. My little network is up and running with TCP/IP as its only protocol. DNS and DHCP are working just fine too. I am just not exactly sure what the problem was.
I am going over all my troubleshooting steps to try to figure it out. I went through all the suggestions given in these posts. I re-installed TCP/IP half a dozen times and even replaced the NIC.
Thanks for all the help. Now I can ask all my other questions.
Trebor |
|
|
|