Re: 'Users' share only visible on server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

LevT <levt@xxxxxxxxxxxxx> wrote:
My event logs are clean, I have SBS 2003 SP1 yesterday updated to R2,

C:\>ipconfig /all

îÁÓÔÒÏÊËÁ ÐÒÏÔÏËÏÌÁ IP ÄÌÑ Windows

éÍÑ ËÏÍÐØÀÔÅÒÁ . . . . . . . . . : DED
ïÓÎÏ×ÎÏÊ DNS-ÓÕÆÆÉËÓ . . . . . . : burzhui-mudaki.lan
ôÉÐ ÕÚÌÁ. . . . . . . . . . . . . : hybrid
IP-ÍÁÒÛÒÕÔÉÚÁÃÉÑ ×ËÌÀÞÅÎÁ . . . . : yes
WINS-ÐÒÏËÓÉ ×ËÌÀÞÅÎ . . . . . . . : no
ðÏÒÑÄÏË ÐÒÏÓÍÏÔÒÁ ÓÕÆÆÉËÓÏ× DNS . : burzhui-mudaki.lan
burzhui-mudaki.su

Local area connection - Ethernet ÁÄÁÐÔÅÒ:

DNS-ÓÕÆÆÉËÓ ÜÔÏÇÏ ÐÏÄËÌÀÞÅÎÉÑ . . :
ïÐÉÓÁÎÉÅ . . . . . . . . . . . . : VMware Accelerated AMD PCNet
Adapter æÉÚÉÞÅÓËÉÊ ÁÄÒÅÓ. . . . . . . . . : 00-0C-29-AE-03-E4
DHCP ×ËÌÀÞÅÎ. . . . . . . . . . . : ÎÅÔ
IP-ÁÄÒÅÓ . . . . . . . . . . . . : 192.168.1.2
íÁÓËÁ ÐÏÄÓÅÔÉ . . . . . . . . . . : 255.255.255.0
ïÓÎÏ×ÎÏÊ ÛÌÀÚ . . . . . . . . . . :
DNS-ÓÅÒ×ÅÒÙ . . . . . . . . . . . : 192.168.1.5
192.168.1.2
ïÓÎÏ×ÎÏÊ WINS-ÓÅÒ×ÅÒ . . . . . . : 192.168.1.2

Internet connection - Ethernet ÁÄÁÐÔÅÒ:

DNS-ÓÕÆÆÉËÓ ÜÔÏÇÏ ÐÏÄËÌÀÞÅÎÉÑ . . : burzhui-mudaki.su
ïÐÉÓÁÎÉÅ . . . . . . . . . . . . : VMware Accelerated AMD PCNet
Adapter æÉÚÉÞÅÓËÉÊ ÁÄÒÅÓ. . . . . . . . . : 00-01-02-51-00-2B
DHCP ×ËÌÀÞÅÎ. . . . . . . . . . . : no
IP-ÁÄÒÅÓ . . . . . . . . . . . . : 87.95.156.26
íÁÓËÁ ÐÏÄÓÅÔÉ . . . . . . . . . . : 255.255.255.252
ïÓÎÏ×ÎÏÊ ÛÌÀÚ . . . . . . . . . . : 87.95.156.25
DNS-ÓÅÒ×ÅÒÙ . . . . . . . . . . . : 192.168.1.2
NetBIOS ÞÅÒÅÚ TCP/IP. . . . . . . : disabled


The bad behaviour is no more annoying me on site, may be it is gone
away. But now I view once more the same thing from the client
attached to 192.168.3/24 branch office network.

C:\Documents and Settings\Admin>net view \\DED
ïÂÝÉÅ ÒÅÓÕÒÓÙ ÎÁ \\DED

éÍÑ ÏÂÝÅÇÏ ÒÅÓÕÒÓÁ ôÉÐ éÓÐÏÌØÚÕÅÔÓÑ ËÁË ëÏÍÍÅÎÔÁÒÉÊ


-------------------------------------------------------------------------------
Users äÉÓË (UNC)
ëÏÍÁÎÄÁ ×ÙÐÏÌÎÅÎÁ successfully.


The same SBS viewed from main site:

F:\>net view \\DED
ïÂÝÉÅ ÒÅÓÕÒÓÙ ÎÁ \\DED

éÍÑ ÏÂÝÅÇÏ ÒÅÓÕÒÓÁ ôÉÐ éÓÐÏÌØÚÕÅÔÓÑ ËÁË ëÏÍÍÅÎÔÁÒÉÊ

-------------------------------------------------------------------------------
Address äÉÓË "Access to address
objects" Attachments äÉÓË
ClientApps äÉÓË ëÌÉÅÎÔÓËÉÅ ÐÒÉÌÏÖÅÎÉÑ
Windows Small Business Server
clients äÉÓË õÓÔÁÎÏ×ËÁ ËÌÉÅÎÔÁ Windows
Small Business Server
D äÉÓË
DED.LOG äÉÓË Exchange message tracking
logs faxclient äÉÓË ëÌÉÅÎÔÙ ÏÂÝÅÇÏ ÆÁËÓÁ
(Microsoft) mspclnt äÉÓË
NETLOGON äÉÓË ïÂÝÉÊ ÓÅÒ×ÅÒ ×ÈÏÄÁ
SYSVOL äÉÓË ïÂÝÉÊ ÓÅÒ×ÅÒ ×ÈÏÄÁ
tsclient äÉÓË
tsweb äÉÓË
Users äÉÓË ïÂÝÉÅ ÐÁÐËÉ ÐÏÌØÚÏ×ÁÔÅÌÅÊ
ëÏÍÁÎÄÁ ×ÙÐÏÌÎÅÎÁ successfully.



Two my networks are connected through RRAS VPN site-2-site link (a
BDC 2003 SP1 R2 with DNS at the head office end and a simple member
server at the branch office end with no network services on the
remote site). Also the Computer Browsing and even NETLOGON domain
communication are not working from the remote office client. The
routing and DNS name resolution are OK.

You need to be using WINS - I can't tell whether you are, as the ipconfig
info isn't in English. All clients & servers should have the WINS server
IP....even in the remote office.
NetBIOS over TCP/IP (NetBT) needs to be enabled everywhere, with 0x8 (hybrid
node) - you can give this all out via DNS.

See if that helps.




"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:%23gPgymgcHHA.3648@xxxxxxxxxxxxxxxxxxxxxxx
LevT <levt@xxxxxxxxxxxxx> wrote:
I mean that during some minutes after my server's boot there is only
one share visible on it. It's Users (Users Shared Folder). No
ClientApps, no mspclnt, no NETLOGON...
What is the cause of this?

Check your event logs for errors and report back. Also let us know
what SPs you have on everything, and include an unedited ipconfig
/all from your server.



"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:%23vls2CgcHHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
LevT <levt@xxxxxxxxxxxxx> wrote:
This problem appears after server start, but it can be ignored on
site because all the shares become accessible shortly. But there
is some malign outcome of this behaviour when I connect remote
branch office through VPN Site-to-Site link. So I need to know
what is its cause and how to deal with it.

Please help me.

Can you please provide more specific detail of the symptoms? I
don't know what your post means.



.

Relevant Pages

  • Re: Users share only visible on server
    ... Yes, I'm using WINS on SBS, I have enabled Netbios over TCPIP on only one ... attached to 192.168.3/24 branch office network. ... Windows Small Business Server ... communication are not working from the remote office client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Advice for Remote Office Setup
    ... the remote office may not be satisfactory if you're attempting to move large ... If you have a reliable DSL connection, I'd consider moving the Windows 2003 ... Server, ... I've got a client with a small business office running SBS2003 with 3 ...
    (microsoft.public.windows.server.sbs)
  • Re: Port 1025 RPC /Lsass.exe
    ... Clients use DNS to locate all domain controllers in domain. ... Next thing -- client will try to talk to the DC it chose. ... from command line to see which server authenticated the client. ... We have a branch office with approx 40 users. ...
    (microsoft.public.windows.server.networking)
  • Re: SBS 2003 and Branch Office
    ... Main office will already have the default site, so define a new site for 'branch office' with the IP subnet for those computers. ... Created a site to site VPN connection between the two routers. ... Then transferred the member server to the branch office and setup as ... to set up a remote office with the functionality as follows. ...
    (microsoft.public.windows.server.sbs)
  • Re: Branch Office Authentication?
    ... > 2003 server to a branch office, ... membership by means of their IP address. ... - if the client does not know anything about the domain, ...
    (microsoft.public.windows.server.security)