![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
![]() |

|
| Microsoft windows 2003 error all error and bugs related to microsoft windows 2003 error |
![]() |
|
can't map share from domain name alias???
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Fixed Error!
Posts: 4,202
Join Date: Mar 2007
Rep Power: 6
IM:
|
# shows terminalserver.company.com resolves fine C:\>nslookup terminalserver.company.com Name: terminalserver.company.com Address: 127.0.0.100 # shows share.company.com resolves fine C:\>nslookup share.company.com Name: share.company.com Address: 127.0.0.100 # can browse share via the IP address fine C:\>start \\127.0.0.100\RemoteDrive # can browse share via the domain name terminalserver.company.com fine C:\>start \\terminalserver.company.com\RemoteDrive # CANNOT browse share via the domain name share.company.com???? C:\>start \\share.company.com\RemoteDrive The system cannot find the file \\share.company.com\RemoteDrive. the win2k3 server's "computer name" is "terminalserver" and the full computer name is "terminalserver." if this matters. Why does one domain name work fine but the other doesn't? why doesn't share.company.com work??? the server for some reason cares how the client got there, and "share" doesn't match "terminalserver"? where can I turn this check off? Note 127.0.0.100 is just a loopback for an SSH VPN tunnel. it could be anything |
|
|
|
|
|
|
|
|
#2 (permalink) |
|
Fixed Error!
Posts: 4,202
Join Date: Mar 2007
Rep Power: 6
IM:
|
Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name |
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|