sharing folders in network

I've just added a windows 2003 server to the network.

IP 192.168.102.48 [server2]

he has a shared folder with Everyone with full acess

server2 apears in the network browser

if I try to acess \\server2 it will not be available but if I try \\192.168.102.48 it works perfectly.

Can any one help me troubleshoot this! I'm out of ideas...
HugoFerreiraAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

luv2smileCommented:
What OS is server2?

0
HugoFerreiraAuthor Commented:
server2 is the new w2003 server with IP 192.168.102.48
0
blueivyCommented:
DNS doesn't sound like it's working. I assume it;s not a DC?

Can you ping it using the name (doubtful)? Can you ping anything else by name (I assume you can or you've got lot's of other problems!).

If it's a fixed IP, try stop and start the Netlogon service or reboot.

If it's not a fixed IP, use ipconfig /registerdns instead.

If none of that works, register the A and PTR record in DNS yourself.
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

gjohnson99Commented:
Frist  check the server name on the server
0
georgecooldudeCommented:
ok you probably dont have correct DNS server listed on the NIC card. Common mistake.

control panel, network connections, right click local area connection. Select TCP/IP - Choose propertys. And where it says DNS server just cross referrance this with a machine that is working. Correct the IP and bingo should all be working! =)
0
HugoFerreiraAuthor Commented:
Yes I can ping other things by name.

I'm not an expert in DNS, currently the DNS server is the router. (is it bad?)

the server name must be ok because I can see the computer name in network browser.

and the best part is: after I gain acess once with \\192.168.102.48 the \\server2 starts working in that W98 machine!

0
HugoFerreiraAuthor Commented:
hmm... looking at the router it does seem to be only a proxy DNS. There is no way to even see the ip table. (at least in the web menu)

but I can ping all names ok... why is this guy diferent?
0
gjohnson99Commented:
This is net bios name no a dns name !!!!!
0
HugoFerreiraAuthor Commented:
yes you're right! we're beggining to mix things.

I realy don't think I'll need a DNS in the domain.

Just want for the netbios name to work! Why doesn't it?
0
gjohnson99Commented:
At the comman prompt

type


net view <enter>

see what yuo get
0
georgecooldudeCommented:
HugoFerreira,

Go to the command prompt. (start, run "cmd")

Type:

ipconfig /all


All the computers need to be using the same DNS server. Are they?
0
HugoFerreiraAuthor Commented:
with net view I get server2 also! It's like

------
\\SERVER1
\\SERVER2
\\HUGO
\\..... and so on
0
gjohnson99Commented:
so what not working
0
HugoFerreiraAuthor Commented:
If I
>ping 192.168.102.48
it works but if i

>ping server2
it returns "unknown host"
 
0
gjohnson99Commented:
now your talking dns  not net bios

to fix  add to your host fille

Do a search for  host on c drive

In the hosts file add

192.168.102.48                   server2                 # my server


you need to reboot

done

0
HugoFerreiraAuthor Commented:
but why all other names resolve, but this one doesn't?
0
HugoFerreiraAuthor Commented:
I've done a search for host on a w2000 server and I got
c:\winnt\system32\hostname
c:\winnt\system32\drivers\etc\hosts

is it one of these?
0
gjohnson99Commented:
c:\winnt\system32\drivers\etc\hosts


This is file open with notepad

add line
192.168.102.48                   server2                 # my server


you need to reboot

done
0
HugoFerreiraAuthor Commented:
I can understand that that would solve the problem for this computer.

But what about the rest of the network!! Doing this in every one is not a good solution because it doesn't attack the source of the problem.

Every other computer uses NetBios well, I would like to understand why doesn't this one?
 
0
georgecooldudeCommented:
Hugo,

Did you ever check my suggestion about DNS? You've not given me feedback but are claiming nothing works.

0
HugoFerreiraAuthor Commented:
But i never needed DNS. They're in a workgroup.

They have always worked without a DNS server!
0
georgecooldudeCommented:
Yes, but if you have entrys there will be checked first and netbeiu will most likely get left out!!

Do you have any DNS entrys filled in on each machine?

If Im trying to help, then its polite to give feedback. You just left this thread...
0
georgecooldudeCommented:
And seeing as you have a windows 2003 machien on your network I assume that uses DNS. What is the role of this machine
0
HugoFerreiraAuthor Commented:
Thank you for your help george.

I tried to do some DNS "tricks" but nothing worked... well I'm far from expert in that...

Active directory as worked for 3 years with no needed maintenance, with a 2000 server machine as domain server and with no "DNS server".

When a router was introduced the ISP guys just pointed the DNS of the PC's to the router. And it seemed to work fine...

Due to some changes, the ISP guys came back recently (after my initial posts) and asked to change the DNS servers to WAN IP's.

The point is: (w98 machines)
In neither of this dns configs and even in PC's with no DNS entrys
>ping server2
returns unknown host.

Please correct me if I'm wrong but I think this is about NETBIOS and not NETBEUI... or am I just making a big mess??
 
0
gjohnson99Commented:
You can not use ping to ping a netbios Name !

If you ping a name, ping need to be able to resolve the name.  

Way to do this are

1. hosts file on local computer.
2. DNS server  -  I think WINS server can also this, but I don't know that much WINS  -  It is windows name server.


 
0
HugoFerreiraAuthor Commented:
Thanks gjohnson99. There is a reason for the ping not to work!!

But how have they all worked for 3 years between all w98, XP machines and the w2000 server??? only the 2003 server was different!
0
gjohnson99Commented:
Have you Been using WINS ?
0
georgecooldudeCommented:
windows 2003 uses DNS and nothing but DNS
0
HugoFerreiraAuthor Commented:
So in that case I do need to setup a DNS server...

I'll try to do that and I'll post back
0
HugoFerreiraAuthor Commented:
gjohnson99:

I don't know what WINS is...
0
georgecooldudeCommented:
Is it a domain controller, the windows 2003 machine?

Its very probably you need a DNS server running somewhere if you choose for it to be the domain controller.

What are the roles of your win 2000 and win 2003 computers? Servers? Active Directory? Email?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
HugoFerreiraAuthor Commented:
the domain controller is the w2000 server.

I'm thinking on first making the experience of adding DNS role to the 2000 server.

If it works, step 2 will be making the 2003 server the domain controller and DNS server and leave the w2000 server only with SQL.

The 2003 server is currently runing merak mail server with no problems.

I never felt the need for DNS, only the machines that connect  to the internet have the DNS pointed to 2 ISP machines.
0
harleyjdCommented:
My CV opinion above is based on my expert opinion - You gotta have DNS for a domain, no ifs, ands or buts.

It's gotta support Dynamic Updates, W2k and W2k3 DNS support this, as do the most common 'nix DNS as long as you have control over them, the router DNS won't.

W2k, W2k3 and WXP look for hostnames by DNS First and Foremost, Netbios is down the tree a bit.

WINS would have helped, but it's a poor cousin to DNS. (Actually more like a poor Great Great Uncle, but lets not go there)

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.