Re: Client PCs and NAS not visible on server


Sometimes I hate spell checkers. COMPATIBILITY, not comparability.

--
Larry Struckmeyer
Get your SBS Health Check
at www.sbsbpa.com


"Larry Struckmeyer [SBS MVP]" <lstruckmeyer@xxxxxxxxxxxxxxx> wrote in
message news:uMrhiM7EKHA.3480@xxxxxxxxxxxxxxxxxxxxxxx
The server looks OK, except I question your choice of a routable ip scheme
for the external nic. Better if this were 192.168.XX.YY, where xx is not
16. You should change both your edge device and the SBS nic2 to a non
routable ip. This is SBS 2003, yes?

Is the workstation Vista? Do you have an XP station. If so, post it up.

I ask, because unless you have installed all the Vista comparability stuff
on both the SBS and the Vista station, you will have issues.

http://support.microsoft.com/kb/926505

http://www.microsoft.com/downloads/details.aspx?FamilyID=9bf2f1e4-1b2c-471b-a284-e0c8c169fac3&displaylang=en

--
Larry Struckmeyer
Get your SBS Health Check
at www.sbsbpa.com


"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6E2DCA51-1B5D-48AD-AF4F-E208591FB619@xxxxxxxxxxxxxxxx
Windows IP Configuration for Server



Host Name . . . . . . . . . . . . : server1

Primary Dns Suffix . . . . . . . : domain.local

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes

DNS Suffix Search List. . . . . . : domain.local



Ethernet adapter Server Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection

Physical Address. . . . . . . . . : 00-0E-0C-4A-C2-FA

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.16.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.16.2



Ethernet adapter External Network Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #2

Physical Address. . . . . . . . . : 00-0E-0C-4A-C2-FB

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 10.0.0.14

Subnet Mask . . . . . . . . . . . : 255.0.0.0

Default Gateway . . . . . . . . . : 10.0.0.2

DNS Servers . . . . . . . . . . . : 192.168.16.2

NetBIOS over Tcpip. . . . . . . . : Disabled



Windows IP Configuration for Client

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain.local
Description . . . . . . . . . . . : Realtek RTL8168C/8111C Family PCI-E
Gigabit Ethernet NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1D-7D-4D-80-F0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::59a1:f253:beba:a7ec%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.16.14(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, August 02, 2009 5:47:12 PM
Lease Expires . . . . . . . . . . : Monday, August 10, 2009 5:47:13 PM
Default Gateway . . . . . . . . . : 192.168.16.2
DHCP Server . . . . . . . . . . . : 192.168.16.2
DHCPv6 IAID . . . . . . . . . . . : 134225277
DNS Servers . . . . . . . . . . . : 192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . : domain.local
Description . . . . . . . . . . . : isatap.domain.local
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::5efe:192.168.16.14%13(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.16.2
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

--
Thanks for the help
Jack


"Larry Struckmeyer [SBS-MVP]" wrote:

Fix the issues found by the BPA.

from the SBS, open a command prompt and type:

ipconfig /all > c:\iptest.txt

Do the same from a workstation.

Find the iptest.txt files on the C drive of the SBS and the workstation,
copy the unedited results from each to your next post here, and let us
know
which is which. No need to change anything, but you could change the
name
of the server and of the domain if you feel you must.

BTW, I normally allow the workstations to print directly to ip printers.
But others don't, preferring to manage the spooler from the server. I
prefer to keep the load off the server, particularly where users are
printing large documents/reports.

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com


"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D2978C93-2512-401D-A10F-C937AB9A47FE@xxxxxxxxxxxxxxxx
I have run BPA and the results follow :

Windows SharePoint Services 2.0 RTM version installed.
This server is running Windows SBS 2003 Service Pack 1 (SP1) and the
RTM
version of Windows SharePoint Services 2.0. Windows SharePoint
Services
2.0
SP1 is a pre-requisite for Windows SBS 2003 SP1.

Task Offloading is enabled
Task Offloading is enabled and should be disabled on Windows Small
Business
Server 2003. Change the value of the DisableTaskOffload registry key
to 1.
For detailed instructions, see the Knowledge Base article "You
experience
intermittent communication failure between computers that are running
Windows
XP or Windows Server 2003" at
http://go.microsoft.com/fwlink/?LinkId=95149.
If the DisableTaskOffload registry key does not exist, then manually
create
this registry key and set its value to 1.

Windows SharePoint Services 2.0 RTM version installed.
The RTM version of Windows SharePoint Services 2.0 is installed on
this
server. Windows SharePoint Services SP3 is available.

DHCP seems to be working. If you have a method to verify this let me
know.
WINS could be set incorrectly. How to I verify this ?
Adding a manual port to the printer works from PC on netrwork printer.


--

Jack


"Larry Struckmeyer [SBS-MVP]" wrote:

Probably two different issues. Server 2003 really needs WINS to
browse
successfully, and of course the SBS should be the DHCP server, so
check
both
of those things.

If you can't browse to the server you aren't going to see shared
printers,
but what happens if you add the tcp/ip port to the workstations and
then
add
the printer to that port manually.?

And, don't forget the SBSBPA.


--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com


"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:753C0A0D-306C-4F2A-8024-6BD8AC0155E5@xxxxxxxxxxxxxxxx
The printer drivers are installed on the server and the printers
have
their
own fixed IP address outside the DHCP allocation and connected to
the
network
directly. I can ping the printer successfully from the server and
client
pc.
I have run CEICW and turned off the firewall.
The NAS is also connected directly to the network and is allocated
an
IP
within the DHCP allocation.
PC, Server, printers and nas are in the same subnet. PCs can see
other
PCs
and server but server cannot see itself or any other PCs. I can
also
print
to
a network printer from the server and print a test page from PCs
(via
explorer - network). The PCs cannot find the printer when I go to
"add
printer" to add the network printer to the PC.
--
Thanks.
Jack


"Larry Struckmeyer [SBS-MVP]" wrote:

Jack:

What method is used to access the printers? Are the ip printers,
with
each
workstation printing to them directly? Printers that are shared
from
the
SBS or the workstations? Directly attached to the workstations?
Have
they
ever worked?

If the NAS and all the printers cannot be found from the server or
any
workstation, I wonder if they are on a different subnet? Can you
ping
any
of thesed devices from anywhere?

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com


"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E79D18AE-4976-4E95-A4DA-2C14ACE34E15@xxxxxxxxxxxxxxxx
I am not sure that this is part of the same problem.
The printers on the server cannot be accessed by the client pc
(This
is
after a connectcomputer without profile or emails being loaded).
However
the
server printers are visible on the client pc in windows
explorer-
network.
--

Jack


"Larry Struckmeyer [SBS-MVP]" wrote:

In order for us to be able to give you the best assistance we
can
it
may
be
helpful for you to ask a question, get one or more answers,
apply
that,
and
then ask another question. Sort of a linear problem solving
one at
a
time
progression. When you post an issue, then never say that
problem
is
resolved and come back hours later with two different ones, it
gets
hard
to
know where you are.

Did you see my response to your prior question about how to
deal
with
the
..ost file, did you open it and copy the contents to a .pst, or
have
you
moved on to some where else, and if so where?

--
Larry
Please post the resolution to your
issue so that others may benefit.

Get a Health Check for SBS at:
www.sbsbpa.com


"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:95EA641A-9138-491C-907F-6F57E2AB3B2F@xxxxxxxxxxxxxxxx
Yes I have gone the route of a re format. The reasons follow
:
With the Symantec clone - the Server restatred; which I
considered
unsuccessful.
With shadow point - the administrators account was not
accessable -
It
could
have been something that I done incorrectly or there could
have
been
a
latent
problem on the server.
As time was against me I opted the 40Hr route. I do apologise
for
for
tying
the loose ends in previous posts as I was uncertain of my
results
and
did
not
want to mislead.
Back to the issues on hand.
The limp along (cached credentials) method was chosen out of
necessity;
to
allow client / server access. At this point in time there are
two
main
areas
of concern :
1. To merge old email cached on the client pc with the new
email
on
the
server. ( I do not need the old cached email on the server)
2 After a successful connectcomputer the client pc must have
its
old
profile.

I assume that the server is installed correclty ( after a
mishap
with
the
DHCP and related events). All seems to be fine. I can RWW,
OWA,
mstsc
(XP
fine, except on Vista but thats OK for now).

The installation seems successful ( I don't know what I don't
know -
ignorance is blis)
I will be greatful for assistance with these two issues.
(I know that when clients fail to authenticate a backup
profile
is
created
which can be fixed via the registry on the pc. This is my
line of
action
to
restore the client profile to the pc after connectcomputer. I
worry
about
the
SIDs and the Shared Users Folders on the server.)
--
Thanks for the post
Jack


"Merv Porter [SBS-MVP]" wrote:

Jack,

You've got half a dozen threads running since your first
post
about
the
RAID
rebuild a few days ago. I haven't seen any that say: "OK.
Ivve
restored
the server using this method and all is good with no errors
on
the
SBS
server". In fact, rather than a restore, it now appears
that
you
built a
whole new domain (a fresh install).

And from one of your other posts, this is disturbing....

I created user accounts as per old but not the computer
as
yet
on
the
server. The client PC logs on to the server with username
and
password
MINUS
THE NETWORK CABLE. When the client PC loads, the network
cable
in
connected
to the pc. The client PC can now see the server and files
on
it.

This client is logging on (with cached credentials) to the
'old
server',
even though that server doesn't exist anymore. He can see
shares
on
the




.

Relevant Pages

  • Re: Cannot connect client to server 2003
    ... you need to reconfigure the IP schema of your SBS ... On the SBS 2003 Server open the Server Management console. ... On the Connection Type page, click Broadband, and then click Next. ... Alternate DNS server, type the IP addresses that are provided by your ISP ...
    (microsoft.public.windows.server.sbs)
  • Re: 2nd Branch Server and Laptop configuration suggestion
    ... please share all printers and folders the laptop user ... This newsgroup only focuses on SBS technical issues. ... now, that way, each branch is independent of any possible Server down at ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... seleting full time broadband connection. ... Les Connor [SBS Community Member - SBS MVP] ... check the router as well and unless I missed a firewall setting on it, ... Anyway the Server Ipconfig /all is this... ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Anyway the Server Ipconfig /all is this... ... Server Local Area Connection: ... Les Connor [SBS Community Member - SBS MVP] ... First Page of the Internet Connection Wizard, ...
    (microsoft.public.windows.server.sbs)
Loading