File Sharing not working

[Jessie]

I installed a new server and put in it a domain, created a
shared needed to install software and I can not see the
share from any workstation. If I go to another server I
can see the share, what's the deal it shouldn't be this
hard is it the workstations or a server or security on
the server? Have set everyone as ADMIN and it still don't
work

HELP!!!
Jess

 

[Steven L Umbach]

That sounds like a problem with the browse list possibly not being updated
yet or a networking problem. It would not be a pemission problem. Try using
unc to see if you can connect from a workstation using the the servers ip
address such as \\xxx.xxx.xxx.xxx\sharename. --- Steve

 

[Guest]

Yes, this worked but now what? How do I fix it
thanks cause I'm pulling my hair out on this one
Jess

 

[Steven L Umbach]

Hi Jessie. Browse problems usually occur when a computer can not see a
computer on another subnet because the browse masters can not communicate
since they need wins to find each other. Browse problems also happen if
workstations can not find the browsemaster because they are not using wins
if subnets are involved or the browsemaster [usually a server/pdc fsmo] is
not a wins client, or if the browsemaster has more then one nic. Browsing
problems are a real headache. I will leave a couple links and you may want
to post in the win2000.networking newsgroup. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;EN-US;102878
http://support.microsoft.com/default.aspx?scid=kb;EN-US;188305
http://support.microsoft.com/?kbid=188001

 

[Guest]

Steve, I tried the browstat and it comes back as a unknown
command is there anything special or which server to run
it on?
JEss

-----Original Message-----
Hi Jessie. Browse problems usually occur when a computer can not see a
computer on another subnet because the browse masters can not communicate
since they need wins to find each other. Browse problems also happen if
workstations can not find the browsemaster because they are not using wins
if subnets are involved or the browsemaster [usually a server/pdc fsmo] is
not a wins client, or if the browsemaster has more then one nic. Browsing
problems are a real headache. I will leave a couple links and you may want
to post in the win2000.networking newsgroup. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;EN- US;102878

http://support.microsoft.com/default.aspx?scid=kb;EN-

US;188305
http://support.microsoft.com/?kbid=188001

Yes, this worked but now what? How do I fix it
thanks cause I'm pulling my hair out on this one
Jess
possibly
not being updated pemission
problem. Try using

.

 

[Guest]

Steve,
I added NETBEUI and it works. Shouldn't have had to do
this????

strange stuff

 

[Steven L Umbach]

You have to download it. It is available here
http://www.petri.co.il/download_free_reskit_tools.htm . --- Steve

Steve, I tried the browstat and it comes back as a unknown
command is there anything special or which server to run
it on?
JEss

-----Original Message-----
Hi Jessie. Browse problems usually occur when a computer can not see a
computer on another subnet because the browse masters can not communicate
since they need wins to find each other. Browse problems also happen if
workstations can not find the browsemaster because they are not using wins
if subnets are involved or the browsemaster [usually a server/pdc fsmo] is
not a wins client, or if the browsemaster has more then one nic. Browsing
problems are a real headache. I will leave a couple links and you may want
to post in the win2000.networking newsgroup. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;EN- US;102878

http://support.microsoft.com/default.aspx?scid=kb;EN-

US;188305
http://support.microsoft.com/?kbid=188001

Yes, this worked but now what? How do I fix it
thanks cause I'm pulling my hair out on this one
Jess

-----Original Message-----
That sounds like a problem with the browse list possibly
not being updated
yet or a networking problem. It would not be a pemission
problem. Try using
unc to see if you can connect from a workstation using
the the servers ip
address such as \\xxx.xxx.xxx.xxx\sharename. --- Steve


I installed a new server and put in it a domain,
created a
shared needed to install software and I can not see the
share from any workstation. If I go to another server I
can see the share, what's the deal it shouldn't be this
hard is it the workstations or a server or security on
the server? Have set everyone as ADMIN and it still
don't
work

HELP!!!
Jess


.

.

 

[Brian Gibson]

First off I would get rid of NetBEUI, it is a legacy
protocol that wil just throw a bunch of unwanted traffic
on your network.

If this is a Windows 2000 (or 2003) domain I have read
that you can publish your shares in Active Directory.
Since Win2k and XP have LDAP querying tools built right
into the OS (and win98 machines can download the AD
querying tools) that will be much more reliable than
relying on master browser, domain master browsers,
elections.....what a pain in the rump.

Also, if most of your machines are win2k or above then
why not put the server's IP in DNS and when people need
to get to the system they just go to start + run and type
in

\\server\share

(or the fully qualified domain name)

\\server.domain.com\share

Lastly, if all of your network clients point to the same
WINS server (or to WINS servers that replicate their
entries with one another) then you can do the "Start"--

"Run" --> UNC share thing listed above. If I were you I

would work towards having your entries in DNS (win2k and
xp clients can be set to update their own entries in DNS
if you like.... if you do not think it is a security risk)

Good luck,
Brian Gibson
Systems Administrator
Wheaton College

-----Original Message-----
Steve, I tried the browstat and it comes back as a unknown
command is there anything special or which server to run
it on?
JEss

-----Original Message-----
Hi Jessie. Browse problems usually occur when a

computer
can not see a

computer on another subnet because the browse masters

can
not communicate

since they need wins to find each other. Browse

problems
also happen if

workstations can not find the browsemaster because they are not using wins
if subnets are involved or the browsemaster [usually a server/pdc fsmo] is
not a wins client, or if the browsemaster has more then one nic. Browsing
problems are a real headache. I will leave a couple

links
and you may want

to post in the win2000.networking newsgroup. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;EN- US;102878
US;188305
http://support.microsoft.com/?kbid=188001

see

the

security

on


.

.

 

[Steven L Umbach]

No you do not need netbeui, as a matter of fact you should make sure it is not on any
computers unless you need it for a particular reason. Netbeui will have different
masterbrowsers than tcp/ip will. Rebooting a computer will sometimes speed up browse
list propagation. I would try to find out what your masterbrowsers are and make sure
they are not multihomed and check their Event Viewer logs for any problems. Normally
the domain pdc fsmo is the domain master browser and each subnet has a their own
master browser. Master browsers are identified in the wins database also. --- Steve