workstations can't see server, & vv

I have a new setup of SBS 2003. (It was mostly set up by someone else,
because I'm new at system administration.)

Everything seems to run normally, I added workstations to the domain, and
users are able to log in either locally or to the domain, as was intended.

The problem is, none of the workstations that have been added can see the
server in My Network Places. They can log in to the domain, and they can
access shared folders on the server, but only if the server name is manually
typed in the Add Network Place wizard.

They simply cannot browse and see the server. But they can see other
workstations just fine!

Likewise, the server cannot see the workstations. In Server Management, the
stations are listed properly, and I can manage them remotely. But they do
not show up in Browse. And I have a (server) antivirus program (NOD32) that
is trying to maintain av on the workstations, and it cannot see them either.

What am I doing wrong?

In news:%(E-Mail Removed),
Paul Pedersen <no-(E-Mail Removed)> typed:
> I have a new setup of SBS 2003. (It was mostly set up by someone else,
> because I'm new at system administration.)
>
> Everything seems to run normally, I added workstations to the domain,

Using http://servername/connectcomputer?

> and users are able to log in either locally or to the domain, as was
> intended.

Why would you want local logins? I'd disable them. Users should log into the
domain only.
>
> The problem is, none of the workstations that have been added can see
> the server in My Network Places. They can log in to the domain, and
> they can access shared folders on the server, but only if the server
> name is manually typed in the Add Network Place wizard.

You ought to use a login script anyway - probably easiest to modify
SBS_LOGIN_SCRIPT.bat in \\servername\netlogon and add:

net use * /del
net use x: \\servername\sharename /persistent:no
net use y: \\servername\sharename /persistent:no
net use z: \\servername\sharename /persistent:no

and make sure all user accounts have SBS_LOGIN_SCRIPT.bat as their login
script name in their properties.
>
> They simply cannot browse and see the server. But they can see other
> workstations just fine!
>
> Likewise, the server cannot see the workstations. In Server
> Management, the stations are listed properly, and I can manage them
> remotely. But they do not show up in Browse. And I have a (server)
> antivirus program (NOD32) that is trying to maintain av on the
> workstations, and it cannot see them either.
> What am I doing wrong?

If SBS was set up with its default settings, it should be running WINS. Make
sure the server points to its own IP for WINS and same with all
workstations - best to do this via DHCP on the SBS box - there's an option
(44) for the WINS server, and also 46 (or is it 48???) for 'node type' which
should be 0x8 (hybrid node.)

This will enable NetBIOS over TCP/IP on all the workstations, and make sure
that the SBS box is the master browser. I also usually disable the computer
browser service on all workstations as a matter of course when setting them
up (change the startup type to 'disabled' in services.msc on each
workstation).

Also - although it isn't related to browsing, make sure that the server and
all workstations specify *only* the SBS server's LAN IP for DNS - no
external DNS servers should be there at all. The DNS server running in SBS
should have forwarders to your ISP's DNS servers.

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
>
>
> In news:%(E-Mail Removed),
> Paul Pedersen <no-(E-Mail Removed)> typed:
>> I have a new setup of SBS 2003. (It was mostly set up by someone else,
>> because I'm new at system administration.)
>>
>> Everything seems to run normally, I added workstations to the domain,
>
> Using http://servername/connectcomputer?

Yes.


>> and users are able to log in either locally or to the domain, as was
>> intended.
>
> Why would you want local logins? I'd disable them. Users should log into
> the domain only.

These have been standalone for a while now. And the server is new. I'll
probably more them all to domain only eventually, but I want to have the
server operating properly first. And stable! A couple days ago the server
demonstrated an intermittent problem that I'm convinced is hardware. I
certainly have to get that fixed before everyone's domain only.

BTW, I suspect the motherboard. If I replace the motherboard while keeping
disks etc. the same, is there any chance that running Repair from the CD
will make it work?


>>
>> The problem is, none of the workstations that have been added can see
>> the server in My Network Places. They can log in to the domain, and
>> they can access shared folders on the server, but only if the server
>> name is manually typed in the Add Network Place wizard.
>
> You ought to use a login script anyway - probably easiest to modify
> SBS_LOGIN_SCRIPT.bat in \\servername\netlogon and add:
>
> net use * /del
> net use x: \\servername\sharename /persistent:no
> net use y: \\servername\sharename /persistent:no
> net use z: \\servername\sharename /persistent:no
>
> and make sure all user accounts have SBS_LOGIN_SCRIPT.bat as their login
> script name in their properties.

I'll check that out. Thanks.


>>
>> They simply cannot browse and see the server. But they can see other
>> workstations just fine!
>>
>> Likewise, the server cannot see the workstations. In Server
>> Management, the stations are listed properly, and I can manage them
>> remotely. But they do not show up in Browse. And I have a (server)
>> antivirus program (NOD32) that is trying to maintain av on the
>> workstations, and it cannot see them either.
>> What am I doing wrong?
>
> If SBS was set up with its default settings, it should be running WINS.
> Make sure the server points to its own IP for WINS and same with all
> workstations - best to do this via DHCP on the SBS box - there's an option
> (44) for the WINS server, and also 46 (or is it 48???) for 'node type'
> which should be 0x8 (hybrid node.)

OK, I'll check WINS. Maybe there's a problem with it.


>
> This will enable NetBIOS over TCP/IP on all the workstations, and make
> sure that the SBS box is the master browser. I also usually disable the
> computer browser service on all workstations as a matter of course when
> setting them up (change the startup type to 'disabled' in services.msc on
> each workstation).
>
> Also - although it isn't related to browsing, make sure that the server
> and all workstations specify *only* the SBS server's LAN IP for DNS - no
> external DNS servers should be there at all. The DNS server running in SBS
> should have forwarders to your ISP's DNS servers.
>

Thanks for the suggestions.

In news:(E-Mail Removed),
Paul Pedersen <no-(E-Mail Removed)> typed:
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) ahoo.com> wrote in
> message news:(E-Mail Removed)...
>>
>>
>> In news:%(E-Mail Removed),
>> Paul Pedersen <no-(E-Mail Removed)> typed:
>>> I have a new setup of SBS 2003. (It was mostly set up by someone
>>> else, because I'm new at system administration.)
>>>
>>> Everything seems to run normally, I added workstations to the
>>> domain,
>>
>> Using http://servername/connectcomputer?
>
> Yes.
>
>
>>> and users are able to log in either locally or to the domain, as was
>>> intended.
>>
>> Why would you want local logins? I'd disable them. Users should log
>> into the domain only.
>
> These have been standalone for a while now. And the server is new.
> I'll probably more them all to domain only eventually, but I want to
> have the server operating properly first. And stable! A couple days
> ago the server demonstrated an intermittent problem that I'm
> convinced is hardware. I certainly have to get that fixed before
> everyone's domain only.

Yes - but I have to say, I wouldn't deploy a server at all before I were
certain it would run reliably.
>
> BTW, I suspect the motherboard. If I replace the motherboard while
> keeping disks etc. the same, is there any chance that running Repair
> from the CD will make it work?

Do a full backup first. Might want to post in m.p.windows.server.sbs for
more help, just in case.
>
>
>>>
>>> The problem is, none of the workstations that have been added can
>>> see the server in My Network Places. They can log in to the domain,
>>> and they can access shared folders on the server, but only if the
>>> server name is manually typed in the Add Network Place wizard.
>>
>> You ought to use a login script anyway - probably easiest to modify
>> SBS_LOGIN_SCRIPT.bat in \\servername\netlogon and add:
>>
>> net use * /del
>> net use x: \\servername\sharename /persistent:no
>> net use y: \\servername\sharename /persistent:no
>> net use z: \\servername\sharename /persistent:no
>>
>> and make sure all user accounts have SBS_LOGIN_SCRIPT.bat as their
>> login script name in their properties.
>
> I'll check that out. Thanks.

No prob.
>
>
>>>
>>> They simply cannot browse and see the server. But they can see other
>>> workstations just fine!
>>>
>>> Likewise, the server cannot see the workstations. In Server
>>> Management, the stations are listed properly, and I can manage them
>>> remotely. But they do not show up in Browse. And I have a (server)
>>> antivirus program (NOD32) that is trying to maintain av on the
>>> workstations, and it cannot see them either.
>>> What am I doing wrong?
>>
>> If SBS was set up with its default settings, it should be running
>> WINS. Make sure the server points to its own IP for WINS and same
>> with all workstations - best to do this via DHCP on the SBS box -
>> there's an option (44) for the WINS server, and also 46 (or is it
>> 48???) for 'node type' which should be 0x8 (hybrid node.)
>
> OK, I'll check WINS. Maybe there's a problem with it.

Might be - or not all clients may be registered in WINS. Also might disable
the computer browser services on the workstations.
>
>
>>
>> This will enable NetBIOS over TCP/IP on all the workstations, and
>> make sure that the SBS box is the master browser. I also usually
>> disable the computer browser service on all workstations as a matter
>> of course when setting them up (change the startup type to
>> 'disabled' in services.msc on each workstation).
>>
>> Also - although it isn't related to browsing, make sure that the
>> server and all workstations specify *only* the SBS server's LAN IP
>> for DNS - no external DNS servers should be there at all. The DNS
>> server running in SBS should have forwarders to your ISP's DNS
>> servers.
>
> Thanks for the suggestions.

Good luck.

Paul Pedersen wrote:
> I have a new setup of SBS 2003. (It was mostly set up by someone else,
> because I'm new at system administration.)
>
> Everything seems to run normally, I added workstations to the domain, and
> users are able to log in either locally or to the domain, as was intended.
>
> The problem is, none of the workstations that have been added can see the
> server in My Network Places. They can log in to the domain, and they can
> access shared folders on the server, but only if the server name is manually
> typed in the Add Network Place wizard.
>
> They simply cannot browse and see the server. But they can see other
> workstations just fine!
>
> Likewise, the server cannot see the workstations. In Server Management, the
> stations are listed properly, and I can manage them remotely. But they do
> not show up in Browse. And I have a (server) antivirus program (NOD32) that
> is trying to maintain av on the workstations, and it cannot see them either.
>
> What am I doing wrong?
>
>
>
Is NETBios enabled on the sbs server?