Server glitch - whats causing this?

[TheCake]

My server has an IP of 192.168.2.2

If I type into the address bar \\server it lists the shares on it. It shows 3 shares which is not right there should be loads.

If I type into the address bar \\192.168.2.2 it lists loads and loads of shares on it. Woohoo.

How can I get all the shares to show under \\server. Its only just started doing this and I'm totally baffled.

Thanks. Urgent!

 

[TheCake]

I'm thinking localhost DNS? Thoughts?

 

[Rasclart]

Sounds like DNS

Is this Server 2003? I assume its handling DNS? Try flushing DNS, clearing DNS cache cant remember the option.

Bizarre though it resolves all shares through the IP. Are you getting this on another PC? i.e Accessing the server from a PC, have you checked the DNS settings are right. Not pointing to the router for DNS rather than the server

 

[TheCake]

Pretty much.

The shares exist on a 2003 Server, i'm trying to access them from our 2000 Server. 2003 server handles the DNS.

 

[Pete]

Servername issue will be netbios not dns, do you have WINS installed and configured. MS will claim it's not needed but it is! lol

 

[TheCake]

Thanks Pete. I was just sat thinking this feels more like there ar 2 computers both called server.... if you catch my drift.

I'm just checking on the Wins config. Any pointers would be appreciated.

 

[Rasclart]

Listen to Pete he knows more. I hate Pete

We have several servers without WINS and it seems to work fine? What would netbios not be doing?

 

[@Spoonie]

bring up a command prompt (Start -> Run -> CMD), now pring server:

C:\> ping server

Does this return the correct IP Address?

 

[Rasclart]

Beat me to it. Was going to say see what Serve resolves to. But I doubt very much thats the problem

As if there was a conflict he would know about it being that its a Server platform.

 

[Pete]

Could always try the FQDN as well and see what shares you can see then.

 

[TheCake]

I think I've got it....

One of the remote sites which connects 'might' have a server there called "server". This is making the DNS go mental. Hence when i type 'server' in its going to the offsite 2000 server and if I type the IP in its going to the 2003 server.

Sound feasible? They connect in over VPN. Can I tweak netbios at the main server end to stop this happenening and any Windows 2000 Server to Windows 2003 Server traffic stay there?

Like adjusting the hosts record?

 

[@Spoonie]

Change the name of your server, quickest solution if theres another machine with the same name that you don't control, you could add an entry to the hosts files on the 2000 box but this will only resolve the name resolution issues for that machine.

 

[Pete]

Is the FQDN of the two servers the same and do they use the same DNS server, you may want to turn off auto dns entries/registration for those two servers.

 

[TheCake]

Pete - what the f**k is FQDN, what does it do and how do I use it.

 

[TheCake]

Fully Qualified Domain Name.. .right looking at it now :

 

[TheCake]

The plot thickens. Its looking increasingly likely that there are either 2 machines BOTH replying to the name "server" or 2 machines with the same IP address. I guess the latter is quite unliekly or else a pop up error would eccur, but 2 machines with the same name... on the same network - but not same domain, 1 is a workroup... could this cause a monster glitch like this?

 

[Rasclart]

Can you temp disable the VPN connection then try accessing the shares again!

 

[TheCake]

I'm hoping to get said machine turned off. We've narrowed it down from a building full to a selection of 3 coming from their Manchester office. I'm thinking as soon as its powered down it should be fine!?! Maybe...

 

[@Spoonie]

I would change the name, using 'server' could result in you facing similar issues further down the line.

 

[TheCake]

Right fixed it! Woo. Will change server names this weke. Thats guys. You all deserve a drink at lunch cheers.

 

[KDF]

Its normally not a good idea to call a server "server" as some other person has normally already thought of that but you probably know that now.. heh.

 

[Rasclart]

Glad its sorted. Is this a new server as surely this would have showed its ugly head before!