Problem with name resolution

I've recently had to rebuild a clients main server which is Windows 2000
Small Business Edition. The domain name used to be example but now I've made
it example.local.

All of the machines can be successfully added to the domain however the two
Windows XP machines when trying to search for shares on \\Server come back
with none, I have to put in the FQDN \\Server.example.local. This is
affecting roaming user profiles, shares, login scripts and networked
printers. When I ping the server name it resolves to server.example.local.
I've add the DNS suffix .example.local in but this doesn't make a difference.
If I try a search for shares on \\gateway it picks up the shares successfully
and the same for any workstation shares.

I've tried building a new Windows XP machine but it has the same problem, I
was thinking it had something to do with the workstations.

Please help.

.

Relevant Pages

  • Re: VPN access to network file shares
    ... "The file shares are on a server running Windows Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Fileserver question
    ... >> another box running both 9.0 and Windows. ... >> computers in the same room and connected to a router. ... otherwise you will need to run a DHCP server on one ... > of the machines, preferably the server, or give both machines static ...
    (alt.os.linux.suse)
  • Re: Windows domain user is sometimes denied access to server share
    ... I would also check the server with the share security log ... He can access the shares that do not have security on them OK, ... with windows user and or windows group accounts. ...
    (microsoft.public.windows.server.security)
  • nslookup times out on some WinXP clients
    ... Basically, nslookup times out on some Windows machines, but not on others. ... we currently have a Windows 2000 Server DNS & DHCP Server serving IP ...
    (RedHat)
  • Re: New: LanMan98 V2 Not connecting
    ... all) Windows machines, the computer name as found in the system ... essentially Windows was rejecting the connection because it hadn't ... LanMan98 appears to be one, ... uses a low-level message protocol called SMB (Server Message Block). ...
    (comp.sys.acorn.networking)