![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Why can't I get any Vista (even Business and Enterprise) version to accept a
FQDN user logon into an AD file share? It only works with pre-Windows 2000 user logon name. If the client is on the domain I can log into the workstation with FQDN and then access file shares the logged in user has rights too. However if a share is accessed from a Vista client not attached to the domain I am forced to use the pre-Windows 2000 logon name. XP clients not attached to the domain did not have this limitation, FQDN names work with XP. Thanks for the attention to this question in advance. |
|
|||
|
Sounds like DNS issue. Any error if using nslookup? Do you have FQND if you
ping a host? -- Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "Dewd" wrote in message news ![]() Why can't I get any Vista (even Business and Enterprise) version to accept a FQDN user logon into an AD file share? It only works with pre-Windows 2000 user logon name. If the client is on the domain I can log into the workstation with FQDN and then access file shares the logged in user has rights too. However if a share is accessed from a Vista client not attached to the domain I am forced to use the pre-Windows 2000 logon name. XP clients not attached to the domain did not have this limitation, FQDN names work with XP. Thanks for the attention to this question in advance. |
|
|||
|
Yes, DNS the proper DNS suffix is assigned to the client and working. It's
not about the file share access using the file share name, it's about the authentication. In Vista, the AD fileshare logon prompt only works with, for example, "Domain\jsmith" instead of " however " works fine in XP. This is something I can bring up later with my premier support for Microsoft but I figure I'd see if this was a known issue first. My searches in the Knowledge base and searches find nothing. Thanks for the attention in this matter. Ed Kulb Stryker Orthopaedics Sr. Network Administrator "Robert L. (MS-MVP)" wrote: Sounds like DNS issue. Any error if using nslookup? Do you have FQND if you ping a host? -- Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com "Dewd" wrote in message news ![]() Why can't I get any Vista (even Business and Enterprise) version to accept a FQDN user logon into an AD file share? It only works with pre-Windows 2000 user logon name. If the client is on the domain I can log into the workstation with FQDN and then access file shares the logged in user has rights too. However if a share is accessed from a Vista client not attached to the domain I am forced to use the pre-Windows 2000 logon name. XP clients not attached to the domain did not have this limitation, FQDN names work with XP. Thanks for the attention to this question in advance. |
| Thread Tools | |
| Display Modes | |
|
|