Having to use FQDN for server name instead of host name

[rooster9]

Hello everyone,
Here is my issue:
Client: XP Pro
Member Server: Server 2000 (not a DC)(both on AD domain)
Trying to access resources over network (printers, shares, etc...) (using the UNC path) from client and I keep having to use the FQDN name of servers instead of just the host name. I have created entries in the host file on the client machine in hopes of resolving having to use the FQDN for every resource. (ex. \\pc-name instead of \\pc-name.domain.com). Connecting to printers I keep getting an access denied message. These issues persist even if I am logged on as local administrator or local user with Power User privileges. Microsoft's KB resolutions have not worked for printer issue.
Note: this machine has been ghosted - but so have other machines using the exact same image. The other machines do not have this issue.

Bad NIC or bad driver??? Device Manager indicates no issues. All settings for network are correct.
Could this be a BIOS issue?
Any suggestions would be helpful.
Thanks
Rooster9

 

[bcastner]

Compare the IPCONFIG results from a working and non-working computer.

My guess is the DNS suffix fields will prove to be different.


____________________________
Users Helping Users

 

[rooster9]

FYI - my fix for this solution was to replace the hosts file on the client. The new hosts file included the IP and name of the server - just like the original. Not sure why this worked.
Thanks
Rooster9