Re: What have I done?

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Paul,

Finish the SBS setup, that is what you are missing. SBS has to be a DC. And
XP Home can't join a domain.

--
Regards,

Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53

"Paul2" <Paul2@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:4202279B-1DB7-49F6-B44A-35BBEB2AF2C7@xxxxxxxxxxxxxxxx
I had a similar problem, which has been partially fixed. Now the server
can
see the workstations and vice versa, but clicking on them in Windows
Explorer
gives "<computer name> is not accessible. You may not have permission..."

This is a new installation. The server has not yet been set up as a DC.
But
File and Printer sharing should still work, right? I have to be able to
serve
some printers and files to computers (some WinXP Home) and users who will
never be in the domain.

In addition, other computers on the network cannot see printers shared by
the server.

NetBIOS is on for TCP/IP on the internal nic, and I have cleared all WINS
entries. I have set permissions for printer sharing to Print for Everyone;
yet no workstation can even see the server's printers.

What am I missing?


"Marina Roos [SBS-MVP]" wrote:

Hi,

Enable NetBIOS over TCP/IP on the servernic.
You can delete all records in WINS, they will be recreated
automagically.

--
Regards,

Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53

"Boolean1" <Boolean1@xxxxxxxxxxx> schreef in bericht
news:AZWdneb-V5qIvNzZnZ2dnUVZ_tGdnZ2d@xxxxxxxxxxxxxx

Thanks Marina,

I did check all the NIC's and they are configured for file and print
sharing.

Here's where I am now:

I just did a http://servername/ConnectComputer from the one desktop
that
was
leftover from the server re-install, and now I can use "Manage
Computer"
from the Server to that Client, which I couldn't do before. So that
definetely helped.

I still don't see the clients in the WINS MMC. This seems to have a
bit
of
obsolete information. Can I delete the WINS server and have it
re-register
everything anew?

I still don't see any clients in My Network Places / Enitre Network /
Microsoft Windows Network / domain using Windows Explorer from server.

I still don't see the server in the My Network Places / Enitre Network
/
Microsoft Windows Network / domain using Windows Explorer from the
clients.

Lastly, when looking in Active Directory Users and Computers MMC on
the
server under Domain/MyBusiness/Computers/SBSServers...I don't see the
server
there.

I'm not sure what to do next.

Details of ipconfig /all on the server and two clients are shown
below.

Thanks much,

Boolean1

===========================================

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : dgs027
Primary Dns Suffix . . . . . . . : SyncSolutions.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : SyncSolutions.local
syncsolutions.local

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : syncsolutions.local
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
For
Com
plete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-0A-5E-48-42-33
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.17
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.2
DNS Servers . . . . . . . . . . . : 192.168.0.2
Primary WINS Server . . . . . . . : 192.168.0.2
Lease Obtained. . . . . . . . . . : Saturday, April 15, 2006
11:28:54 AM

Lease Expires . . . . . . . . . . : Sunday, April 23, 2006
11:28:54
AM

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

===================================================

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : sync-lt-002
Primary Dns Suffix . . . . . . . : SyncSolutions.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : SyncSolutions.local
syncsolutions.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : syncsolutions.local
Description . . . . . . . . . . . : Broadcom 570x Gigabit
Integrated
Con
troller
Physical Address. . . . . . . . . : 00-0F-1F-A0-F4-6C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.2
DNS Servers . . . . . . . . . . . : 192.168.0.2
Primary WINS Server . . . . . . . : 192.168.0.2
Lease Obtained. . . . . . . . . . : Friday, April 14, 2006
8:37:30
PM
Lease Expires . . . . . . . . . . : Saturday, April 22, 2006
8:37:30
PM

====================================================

From Server:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : sync001
Primary Dns Suffix . . . . . . . : SyncSolutions.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : syncsolutions.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
Physical Address. . . . . . . . . : 00-11-43-D3-41-7A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.2
Primary WINS Server . . . . . . . : 192.168.0.2
NetBIOS over Tcpip. . . . . . . . : Disabled



"Marina Roos [SBS-MVP]" <marina@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:%23UVsLyJYGHA.2208@xxxxxxxxxxxxxxxxxxxxxxx
Did you rejoin the clients with servername/connectcomputer? Is File
and
printersharing enabled on the server's internal nic and all clients
nics?
Can you post the ipconfig/all from the server and a client?

--
Regards,

Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53

"Boolean1" <Boolean1@xxxxxxxxxxx> schreef in bericht
news:ooudnZR57d94Yt3ZnZ2dnUVZ_smdnZ2d@xxxxxxxxxxxxxx
Thatnks, that's good input.

I'm now looking at the WINS setup. I see a couple of my old
workstations
/
file servers that have been "tombstoned". And also -- the File
Server
of
my
server is in a tombstoned state...that can't be good!!!

Also, don't see my new workstation listed.

Boolean1

"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:eL4QsEFYGHA.456@xxxxxxxxxxxxxxxxxxxxxxx
When you re-installed the server you created a new domain/Active
Directory
which, coincidentally, has the same name as your original AD.
However,
the
PC's don't give a RAT'S HEINEY about the apparent name (eg.
domain.local)
they have a link to something unique, the 'domain SID'. As far as
the
PC's
are concerned your 'same name' AD may as well not exist.

Can I draw an analogy to DNS (is this going to be of benefit or
detriment)? DNS converts 'friendly names' (eg. www.microsoft.com)
to
IP
addresses, which are unique (hopefully). Your Workstations think
the
domain name whatever.local points to SID S5-1234-98765454324554,
your
server has created a new SID and knows whatever.local should be
pointing
to S5-4321-87654087698765763.

The reason you can connect to shares located at
\\servername\sharename
is
that (I believe) you have recreated users in the new domain with
the
same
username/password as the old. This is a process known as 'Pass
Through
Authentication'. It also indicates that you are not implementing
proper
password change/security policies on your network, YOU should not
know
anyone else's password.

"Boolean1" <Boolean1@xxxxxxxxxxx> wrote in message
news:g9mdnWyFbur4G93ZnZ2dnUVZ_tmdnZ2d@xxxxxxxxxxxxxx
I have noticed recently, that since I re-installed SBS 2003 about
eight
weeks ago, and I don't know when this started happening, but I'm
noticing
that when I "browse" using Windows Explorer, and I go to My
Network
Places
/ Entire Network / Microsoft Windows Network / LocalDomainName...

That when I'm on a client, I don't see the server; and when I'm
on
the
server, I don't see any clients. The server doesn't see any
clients!
And it doesn't even see the U.S. Robotics Network Print Server
anymore.

Any ideas on what could be causing this?

I can create Shares on the Server, and connect to them no
problem --
as
long as I manually type in the Share Name:
\\Servername\ShareName --
but
I can't "browse" to it.

It's a problem now that I want to back-up the clients to the
server,
and
the server (wherer Backup Exec is installed) does not see the
clients.

Could this be because of XP Service Pack 2 Firewall? That
doesn't
explain why the clients don't see the server though.

Anything else that could cause this kind of behavior? Trusts?

Thanks in advance for any help.

Regards,

Boolean1
















.

Relevant Pages

  • Re: "server is not accessible"
    ... Do you install the Windows server 2003 sp2 on the SBS or backup server? ... |> Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • RE: Company web
    ... I changed the settings on the SBS, ... Ethernet adapter Server Local Area Connection: ... Connection-specific DNS Suffix. ... But now i cant acces the internet anymore with the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2008 and RWW - cannot connect from remote clients
    ... I understood that using the loopback address sent everything DNS back to the server to handle. ... You will see that it looks to some extent like it has - but it doesn't appear in the SBS console list of computers, and has generated the error message that the domain is unknown. ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)
  • Re: problem connecting to server from XP
    ... As I am new to SBS 2003 I did not know the difference, I thought we were buying the latest version as we changed over from Novel Netware. ... If I were doing a new install today I would want to start with disks that were Windows Small Business Server 2003 w/SP1 as a starting point. ... I wish to add other items in the firewall rules but can not see where to add them without running the "Connect to Internet" wizard. ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS Configuration error
    ... ports from your router to the SBS? ... The server has had all updates ... Ethernet adapter Server Local Area Connection: ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.windows.server.sbs)