DNS issues on 2003 network
-
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
So what are my options here? Are there any other tests I can run?
You could add another DC and DNS to your domain, 2003 is out of support anyway
Probably the way to go. This system is suspect. You need clean builds and new systems. Why fix what is broken when you could actually fix the problems?
-
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
So what are my options here? Are there any other tests I can run?
You could add another DC and DNS to your domain, 2003 is out of support anyway
Yep, this would probably be your best bet.
-
@scottalanmiller said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
So what are my options here? Are there any other tests I can run?
You could add another DC and DNS to your domain, 2003 is out of support anyway
Probably the way to go. This system is suspect. You need clean builds and new systems. Why fix what is broken when you could actually fix the problems?
I would be going from 2003 - 2012 R2. I wanted to do it on my test environment before I did it in a live environment
-
@wirestyle22 said in DNS issues on 2003 network:
I would be going from 2003 - 2012 R2. I wanted to do it on my test environment before I did it in a live environment
There's not much to be afraid of. Add two new DC's, transfer FSMO etc, remove old DC's after a couple of days, upgrade forest level if required, done.
-
@wirestyle22 said in DNS issues on 2003 network:
@scottalanmiller said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
So what are my options here? Are there any other tests I can run?
You could add another DC and DNS to your domain, 2003 is out of support anyway
Probably the way to go. This system is suspect. You need clean builds and new systems. Why fix what is broken when you could actually fix the problems?
I would be going from 2003 - 2012 R2. I wanted to do it on my test environment before I did it in a live environment
Why? It's just a domain migration. I'm not knocking testing, but given the situation and the near pointlessness of testing something so generic and standard, I would not let a lack of testing stop you from fixing the problems.
-
@wirestyle22 said in DNS issues on 2003 network:
@scottalanmiller said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
So what are my options here? Are there any other tests I can run?
You could add another DC and DNS to your domain, 2003 is out of support anyway
Probably the way to go. This system is suspect. You need clean builds and new systems. Why fix what is broken when you could actually fix the problems?
I would be going from 2003 - 2012 R2. I wanted to do it on my test environment before I did it in a live environment
You can do that but DNS, DHCP, and AD are so trivial that you most likely won't have an issue.
-
You can check the Event Viewer on your server with nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
-
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@scottalanmiller said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
So what are my options here? Are there any other tests I can run?
You could add another DC and DNS to your domain, 2003 is out of support anyway
Probably the way to go. This system is suspect. You need clean builds and new systems. Why fix what is broken when you could actually fix the problems?
I would be going from 2003 - 2012 R2. I wanted to do it on my test environment before I did it in a live environment
You can do that but DNS, DHCP, and AD are so trivial that you most likely won't have an issue.
Trivial, non-destructive and standard.
-
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server with nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
No I can't ping it
-
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
-
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
I can't do that safely as per @scottalanmiller
-
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
Wait, something else coming to mind: You can't query the public google DNS (8.8.8.8) from your failing hosts?
-
@thwr said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
Wait, something else coming to mind: You can't query the public google DNS (8.8.8.8) from your failing hosts?
you mean nslookup www.crayola.com 8.8.8.8? No
-
Also, should be mentioned, this is the window in which to consider a Linux DC, instead of WIndows. That Windows 2003 was still running suggests a major issue that can't be fixed by updating now - something stopped people from keeping systems under support and patched for the last decade. That's a really, really big concern. A decade without proper updates? Um, you can't be on Windows. It's that simple, unless there has been a real change at the top that would make the problem go away, you need to apply business logic and realism and look at this correctly.... Linux you can update without management oversight. Windows you cannot. If you install Windows, are you just creating the same problems again? Basically, Windows is a bandaid, Linux would be a fix. Once you install 2012 R2 DCs, Linux is off the table. RIght now, it is still on the table.
-
@thwr said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
Wait, something else coming to mind: You can't query the public google DNS (8.8.8.8) from your failing hosts?
That's why I think it might have to do with SEP. He can't access external resources either.
-
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
I can't do that safely as per @scottalanmiller
That's true, but you can't keep is safely, either.
-
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
Wait, something else coming to mind: You can't query the public google DNS (8.8.8.8) from your failing hosts?
you mean nslookup www.crayola.com 8.8.8.8? No
We need to investigate that. Are you sure that there's no firewall / Norton / Symantec / whatever installed on the print- or fileserver? Because that's not related to your DC.
What kind of internet connectivity do your failing hosts have? Directly outbound via a gateway? Some proxy?
-
@scottalanmiller said in DNS issues on 2003 network:
Also, should be mentioned, this is the window in which to consider a Linux DC, instead of WIndows. That Windows 2003 was still running suggests a major issue that can't be fixed by updating now - something stopped people from keeping systems under support and patched for the last decade. That's a really, really big concern. A decade without proper updates? Um, you can't be on Windows. It's that simple, unless there has been a real change at the top that would make the problem go away, you need to apply business logic and realism and look at this correctly.... Linux you can update without management oversight. Windows you cannot. If you install Windows, are you just creating the same problems again? Basically, Windows is a bandaid, Linux would be a fix. Once you install 2012 R2 DCs, Linux is off the table. RIght now, it is still on the table.
Good point, but honestly, that requires Linux expertise.
-
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
Wait, something else coming to mind: You can't query the public google DNS (8.8.8.8) from your failing hosts?
you mean nslookup www.crayola.com 8.8.8.8? No
We need to investigate that. Are you sure that there's no firewall / Norton / Symantec / whatever installed on the print- or fileserver? Because that's not related to your DC.
What kind of internet connectivity do your failing hosts have? Directly outbound via a gateway? Some proxy?
-
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@momurda said in DNS issues on 2003 network:
You can check the Event Viewer on your server nslookup errors and also on the DC, should be easy to see what the problem is.
If you do an ipconfig /flushdns on your client pc, can you ping the file server afterwards? But yes you should definitely make another dc ratehr than 2003.
5(?) people looked into this and we had to guess a lot because the symptoms didn't make much sense. Event log on the server maybe, but who knows. Getting rid of SEP prior of anything else is his best bet IMHO.
Wait, something else coming to mind: You can't query the public google DNS (8.8.8.8) from your failing hosts?
you mean nslookup www.crayola.com 8.8.8.8? No
We need to investigate that. Are you sure that there's no firewall / Norton / Symantec / whatever installed on the print- or fileserver? Because that's not related to your DC.
What kind of internet connectivity do your failing hosts have? Directly outbound via a gateway? Some proxy?
That doesn't answer my question
Are you using some form of a proxy for outbound internet access? Like MS ISA/TMG, Squid, Astaro etc?
