DNS issues on 2003 network
-
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
-
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
-
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
This command just checks if there is something listening on UDP/53. 53 is the default DNS port, 99% of the DNS requests are served using UDP. Be aware, DNS CAN use TCP too. So yes, use that on your DNS server.
-
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
The IP's are correct
-
@wirestyle22 said in DNS issues on 2003 network:
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
The IP's are correct
Erm, is the .16 a DNS? Same host?
-
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
The IP's are correct
Erm, is the .16 a DNS? Same host?
I was going to say. Is this on the 2003 DC or the File server you are having issues with?
-
@coliver said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
The IP's are correct
Erm, is the .16 a DNS? Same host?
I was going to say. Is this on the 2003 DC or the File server you are having issues with?
My guess is that the .16 is his file- or printserver, so one of the failing ones.
-
@coliver said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
The IP's are correct
Erm, is the .16 a DNS? Same host?
I was going to say. Is this on the 2003 DC or the File server you are having issues with?
Assuming the DC since he said the DC was .16
-
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
The IP's are correct
Erm, is the .16 a DNS? Same host?
.16 is DNS. It's the domain controller
-
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
This command just checks if there is something listening on UDP/53. 53 is the default DNS port, 99% of the DNS requests are served using UDP. Be aware, DNS CAN use TCP too. So yes, use that on your DNS server.
-
@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:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
This command just checks if there is something listening on UDP/53. 53 is the default DNS port, 99% of the DNS requests are served using UDP. Be aware, DNS CAN use TCP too. So yes, use that on your DNS server.
ok, looks good (second last row).
Could you just post a small list with IPs?
DC
Fileserver
PrintserverAre your subnet masks the same on every device?
-
Can you post the TCP/IP settings from the machine you are having an issue with?
-
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@coliver said in DNS issues on 2003 network:
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
netstat -an | findstr /I "udp" | findstr "53"
The only machines that aren't working are the file server and print server. Everything else connected correctly. Am I doing this on the domain controller or problem server?
On the problem server check and see if there are static DNS servers defined. That would be my guess.
The IP's are correct
Erm, is the .16 a DNS? Same host?
.16 is DNS. It's the domain controller
Good to know. How about the configuration of the problem servers.
-
@BRRABill said in DNS issues on 2003 network:
Can you post the TCP/IP settings from the machine you are having an issue with?
File Server
Print Server
-
@wirestyle22 said in DNS issues on 2003 network:
@BRRABill said in DNS issues on 2003 network:
Can you post the TCP/IP settings from the machine you are having an issue with?
File Server
Print Server
Need the DNS data ipconfig /all or go through the details pane like you did previously.
-
Sorry, I mean the same screenshot as you posted for the DC.
-
At least everything is on the same subnet... to sum up:
- You can ping the .16 from .23 and .36 and vice-versa
- You can not use "nslookup somehostname 192.168.10.16"
-
Print Server
File Server
-
@thwr said in DNS issues on 2003 network:
At least everything is on the same subnet... to sum up:
- You can ping the .16 from .23 and .36 and vice-versa
- You can not use "nslookup somehostname 192.168.10.16"
I can't nslookup from .23 or .36, .16 is my domain controller.
Can't ping .16 from either
-
@wirestyle22 said in DNS issues on 2003 network:
@thwr said in DNS issues on 2003 network:
At least everything is on the same subnet... to sum up:
- You can ping the .16 from .23 and .36 and vice-versa
- You can not use "nslookup somehostname 192.168.10.16"
I can't nslookup from .23 or .36, .16 is my domain controller
And you CAN nslookup from everything else? Like the DC itself or your PC?
