buzzard Posted November 6, 2009 Posted November 6, 2009 Right a funny issue has occured in one of our units, the guy who dealt with it is off sick so forgive the holes in this! The Server is the sole DC and is 2003R2. It's domain name (which is wrong) has been set to schoolname.lancs.sch.uk. Now when I type in the run command on the server \\schoolname\dfsshare it works, now from a client it doesn't. This is cocking up all GP as they use DFS for everything The main difference I can see between this and another site is this site has a few DNS Suffix Search Lists which are as follows schoolname.lancs.sch.uk lancs.sch.uk sch.uk All works fine from the server, and if I substitute the domain name for server IP/share the drive mappings work, however anyting that uses the full domain name (virtually everthinng!) fails and fills the local clients event log. all pointing to failure to resolve name/resource unavailable. the Client IP details are identical (bar actual address) to the server. Any suggestions would be appreciated!!!
buzzard Posted November 6, 2009 Author Posted November 6, 2009 (edited) Anyone help, driving me nuts! When I use nslookup from the server to test the loopback address all is working fine.... giving me a headachE!! again when running nslookup on the schoolname.lancs.sch.uk it resolves fine and all is well, but when you type it in the run command just get '\\schoolname.lancs.sch.uk the network path was not found' Edited November 6, 2009 by buzzard
buzzard Posted November 6, 2009 Author Posted November 6, 2009 Now recreated DFS to no avail. has anyone any pointers to what to test, I've tried so many things I can't remember what I've tested!!! The only thing that was changed at the time was stopping students running task manager!
Stuarte Posted November 6, 2009 Posted November 6, 2009 Buzzard, Sounds like it could be a netbios name resolution issue. To start with, try adding an lmhosts entry for the domain on a client and test from the run line again. good luck.
buzzard Posted November 6, 2009 Author Posted November 6, 2009 Thanks for the reply! this is waht I've got from the client C:\>nslookup Default Server: 1117-sr-001.mckee.lancs.sch.uk Address: 10.74.50.230 > set debug > mckee Server: 1117-sr-001.mckee.lancs.sch.uk Address: 10.74.50.230 ------------ Got answer: HEADER: opcode = QUERY, id = 2, rcode = NXDOMAIN header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: mckee.mckee.lancs.sch.uk, type = A, class = IN AUTHORITY RECORDS: -> mckee.lancs.sch.uk ttl = 3600 (1 hour) primary name server = 1117-sr-001.mckee.lancs.sch.uk responsible mail addr = hostmaster.mckee.lancs.sch.uk serial = 3334 refresh = 2600 (43 mins 20 secs) retry = 600 (10 mins) expire = 86400 (1 day) default TTL = 14400 (4 hours) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 3, rcode = NOERROR header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 1, authority records = 0, additional = 0 QUESTIONS: mckee.lancs.sch.uk, type = A, class = IN ANSWERS: -> mckee.lancs.sch.uk internet address = 10.74.50.230 ttl = 600 (10 mins) ------------ Name: mckee.lancs.sch.uk Address: 10.74.50.230 > That all looks fine to me? If I run the full domian name this is where it starts throwing up issues. H:\>nslookup Default Server: 1117-sr-001.mckee.lancs.sch.uk Address: 10.74.50.230 > set debug > mckee.lancs.sch.uk Server: 1117-sr-001.mckee.lancs.sch.uk Address: 10.74.50.230 ------------ Got answer: HEADER: opcode = QUERY, id = 2, rcode = NXDOMAIN header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: mckee.lancs.sch.uk.mckee.lancs.sch.uk, type = A, class = IN AUTHORITY RECORDS: -> mckee.lancs.sch.uk ttl = 3600 (1 hour) primary name server = 1117-sr-001.mckee.lancs.sch.uk responsible mail addr = hostmaster.mckee.lancs.sch.uk serial = 3334 refresh = 2600 (43 mins 20 secs) retry = 600 (10 mins) expire = 86400 (1 day) default TTL = 14400 (4 hours) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 3, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: mckee.lancs.sch.uk.lancs.sch.uk, type = A, class = IN AUTHORITY RECORDS: -> sch.uk ttl = 7952 (2 hours 12 mins 32 secs) primary name server = ns1.nic.uk responsible mail addr = hostmaster.nominet.org.uk serial = 1257431177 refresh = 7200 (2 hours) retry = 300 (5 mins) expire = 2419200 (28 days) default TTL = 10800 (3 hours) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 4, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: mckee.lancs.sch.uk.sch.uk, type = A, class = IN AUTHORITY RECORDS: -> sch.uk ttl = 7952 (2 hours 12 mins 32 secs) primary name server = ns1.nic.uk responsible mail addr = hostmaster.nominet.org.uk serial = 1257431177 refresh = 7200 (2 hours) retry = 300 (5 mins) expire = 2419200 (28 days) default TTL = 10800 (3 hours) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 5, rcode = NOERROR header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 1, authority records = 0, additional = 0 QUESTIONS: mckee.lancs.sch.uk, type = A, class = IN ANSWERS: -> mckee.lancs.sch.uk internet address = 10.74.50.230 ttl = 600 (10 mins) ------------ Name: mckee.lancs.sch.uk Address: 10.74.50.230 > Now this issue appears to be trying to resolve the namespace by going to nominet as the idiots who set it up used the actual web domain name. However this has been working fine for the last 18 months in this setup!!!
buzzard Posted November 6, 2009 Author Posted November 6, 2009 mmm now by adding in the following lines in it was then able to resolve it 10.74.50.230 mckee 10.74.50.230 mckee.lancs.sch.uk Now why isn't thi coming down from the server as it did before, or why's it not resolving through DNS!!!
Stuarte Posted November 6, 2009 Posted November 6, 2009 mmm now by adding in the following lines in it was then able to resolve it 10.74.50.230 mckee 10.74.50.230 mckee.lancs.sch.uk Now why isn't thi coming down from the server as it did before, or why's it not resolving through DNS!!! It doesn't resolve from the run line because its pointing towards ns1.nic.uk and netbios traffic is not (normally) routable. Don't know what might have happened for the problem to pop up now but you need to make sure that you are resolving DNS/netbios traffic locally. Not sure what you need to do to make this happen yet but I'm thinking..... Cheers
jsnetman Posted November 6, 2009 Posted November 6, 2009 Just a question, does your server have a static ip assigned to it? just looking at your IP for the server seems a bit odd. One would normally have a range at the start of your IP Range/DHCP reserved for servers and so on.
jsnetman Posted November 6, 2009 Posted November 6, 2009 QUESTIONS: mckee.lancs.sch.uk, type = A, class = IN ANSWERS: -> mckee.lancs.sch.uk internet address = 10.74.50.230 ttl = 600 (10 mins) I don't undestand this bit 10's IP addresses cannot be on the internet they are private IP's reserved for networks.
jsnetman Posted November 6, 2009 Posted November 6, 2009 It's just the IP address. It doesn't mean it's on the real internet. Yes right nsllookup returns my server Ip the same way. Is your server static or obtain it's IP from DHCP?
buzzard Posted November 6, 2009 Author Posted November 6, 2009 sorry for the delay just been banging my head! The Server IP is static on 230, it's our standard address. if I ping mckee.lancs.sch.uk from the server it resolves to the 230 address, from the client I can ping it as well with it resolving it to 230. This is with hosts files cleared aswell. but if you type run > \\mckee.lancs.sch.uk it gives network path not found message. I'm going mad!
Stuarte Posted November 6, 2009 Posted November 6, 2009 Buzzard -apologies. Just read your post again and realised that my second post is not relevant. Have you got any further? Still think that it would be better if you could resolve the FQDN internally though. Removes many possible points of failure. When you say the domain name is wrong, what do you mean exactly?
buzzard Posted November 10, 2009 Author Posted November 10, 2009 The issue is resolved by rebuilding the PC. There was one machine working fine, same OU all identical. No idea why all bar 1 machine would do this, but a rebuild clears any errors. Regarding the "wrong" name. I never build internal networks with the actual domain name. ie i would use mckee.sch as opposed to the lancs.sch.uk one. That way it would always keep the internal stuff where it's supposed to be. We never commisioned the system, we just get the problems they caused Oh and the server name isn't mckee it's the 1117-SR-001 bit
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now