RNKTechnology
asked on
Server 2008 cannot connect to one specific server
I have one server running server 2008 that cannot "see" one other server by name - only by ip address. When I type \\otherserver - I get a "windows cannot access \\otherserver" error. However, when i type \\192.168.20.8 it is fine.
I have successfully pinged the other server using both name and ip - no problems. Different servers(non running server 2008) can connect to the other server using the name and my server 2008 machine can connect to all other servers by name.
It seems to be a problem just between these two and only going in the one direction. I have turned off the firewalls on both servers.
I have successfully pinged the other server using both name and ip - no problems. Different servers(non running server 2008) can connect to the other server using the name and my server 2008 machine can connect to all other servers by name.
It seems to be a problem just between these two and only going in the one direction. I have turned off the firewalls on both servers.
Have you tried accessing the problem server using its fully qualified domain name (FQDN), so \\otherserver.<domain name>?
Hello,
I have 2 questions for you :)
Did you try to disable SMB version 2 on your server 2008 that you is used as a SMB client?
To use only SMB 1.0 please apply these command lines:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
You will find further information on this link:
http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm
This is not a solution, strictly a troubleshooting step.
Please try to downgrade to version 1 and let me know if you're still having issues with SMB.
In this case I believe the problem is strictly SMB related since you're able to ping other hosts using their hostname without the DNS suffix.
I have 2 questions for you :)
Did you try to disable SMB version 2 on your server 2008 that you is used as a SMB client?
To use only SMB 1.0 please apply these command lines:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
You will find further information on this link:
http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm
This is not a solution, strictly a troubleshooting step.
Please try to downgrade to version 1 and let me know if you're still having issues with SMB.
In this case I believe the problem is strictly SMB related since you're able to ping other hosts using their hostname without the DNS suffix.
No actually I had just one question :) (I answered to the other one myself...)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
First - thanks for all the help - this is my first time actually posting a question although I have used this site many times to get answers.
OK - here is where I am at. At first I was not able to connect using the FQDN. After reviewing the netbios info on the domain - sure enough the ip address of the "other server" had a bad record listed. I ran nbtstat -r on the dc, as well as the two servers in question. After doing that - while I still cannot connect using just \\otherserver I CAN connect using the FQDN.
OK - here is where I am at. At first I was not able to connect using the FQDN. After reviewing the netbios info on the domain - sure enough the ip address of the "other server" had a bad record listed. I ran nbtstat -r on the dc, as well as the two servers in question. After doing that - while I still cannot connect using just \\otherserver I CAN connect using the FQDN.
Ok, you still have a Netbios issue. NBTstat -r only removes the cached WINS / Netbios records locally. The ability to connect via Fully Qualified domain Name relies upon DNS...
WHEN DNS IS USED AND WHEN NETBIOS IS USED:
Within a UNC path if there are more than 15 charactors, and/or there is a period in the middle of the UNC server/computer path you use DNS. If there are no periods and less than 14 charactors, the redirector service queries the Netbios Name Server.....
Example:
Redirector queries DNS when:
\\abcdefghijklmnopqrstuvwx
also
\\servername.domain.com is the path because of the periods in the UNC path
The redirector service queries the Netbios Name server (NBNS) when:
\\Computer because there are less than 15 characters and there are no periods.
If you have WINS, you will also be required to update the WINS resource record.. If you can access the FQDN, and IP, this is strictly a Netbios problem.. Netbios is fickle and if you saw a bad record when you typed NBTSTAT -c, then we have to figure out where that bad cached record came from.. Most likely it's a bad WINS record resolved from a WINS server, OR a bad LMHOST record. At no time should you have a FQDN within the WINS database or an LMHOST record.
WHEN DNS IS USED AND WHEN NETBIOS IS USED:
Within a UNC path if there are more than 15 charactors, and/or there is a period in the middle of the UNC server/computer path you use DNS. If there are no periods and less than 14 charactors, the redirector service queries the Netbios Name Server.....
Example:
Redirector queries DNS when:
\\abcdefghijklmnopqrstuvwx
also
\\servername.domain.com is the path because of the periods in the UNC path
The redirector service queries the Netbios Name server (NBNS) when:
\\Computer because there are less than 15 characters and there are no periods.
If you have WINS, you will also be required to update the WINS resource record.. If you can access the FQDN, and IP, this is strictly a Netbios problem.. Netbios is fickle and if you saw a bad record when you typed NBTSTAT -c, then we have to figure out where that bad cached record came from.. Most likely it's a bad WINS record resolved from a WINS server, OR a bad LMHOST record. At no time should you have a FQDN within the WINS database or an LMHOST record.
ASKER
I do not believe they are running wins on the network - how would I check that.
Ipconfig /all will tell you if there is a WINS server, like it shows existing DNS servers..