UNC path versus mapped drives

[Phillip Windell]

You really ought to ditch the whole "workgroup thing" anyway regaurdless
of

the connection limit. Add a real "server" and create a Domain. Keep the
Domain "simple",...there is not much to it if you keep it simple,...Domains
and Active Directory only become as complex as you personally make
them,...which usually happens when you try to "out smart" the system.

Never mind. I keep forgetting that you are running XP Home. You are just
flat screwed everyway you can cut it. You are using "home user" equipment
and trying to run a commercial network. It just isn't going to
happen,..forget it. You are going to have to throw out everything except
the bare hardware and run XP-Pro on everything then add the hardware for a
Server and run Server2003.

BTW - I saw the question about SQL Server Desktop Engine,...forget
it,...ain't gonna happen. 1. It is for running local databases. 2. It is
*limited* and meant for "personal use" on a single machine during database
developement,...the database has to be moved to a *real* SQL Server for the
whole network to use it after it is developed.

There are no "free lunches".

 

[marsha]

BTW - I saw the question about SQL Server Desktop Engine,...forget
it,...ain't gonna happen. 1. It is for running local databases. 2. It is
*limited* and meant for "personal use" on a single machine during database
developement,...the database has to be moved to a *real* SQL Server for the
whole network to use it after it is developed.

Once again, you are a wonderful source of info!! Thanks!!!

 

[marsha]

You really ought to ditch the whole "workgroup thing" anyway regaurdless of
the connection limit. Add a real "server" and create a Domain. Keep the
Domain "simple",...there is not much to it if you keep it simple,...Domains
and Active Directory only become as complex as you personally make
them,...which usually happens when you try to "out smart" the system.

This is what I have decided to do, BUT the only machine that matters is the
server right??? In other words, it doesn't really matter what OS the users
have, does it???

And as far as putting server software on the server machine, doesn't that
wipe
away the current OS?? Or does it sit as an application on the current OS???
I have already changed the current OS to W2K. We own both. I just don't
understand if the server software, like Windows Server 2003 becomes the OS
or not??

Thanks so much for your exceedingly kind help!!!

 

[GTS]

1. The domain vs. workgroup issue is almost certainly irrelevant to your

I'm gathering that I don't need to set up a domain situation.

It doesn't seem to be a requirement for your program.

Well, I have switched the server to W2K (we own both OS's). But I am
confused
about users. Let me make it very simple. On the computer that holds the
data folder,
I have gone to Control Panel, Users and Passwords and setup each computer
name
as a user with a password. That is the only way that I have ever been
able
to make
this software work. I always see a "Guest" user when I set up the names.
But I have
not used the "Guest" user. To do that would I just have each user
computer
sign in
as Guest??? Is that what that is about??? Would that gain me anything???

That's the right thing to do for Win 2K. I was addressing the use of XP
HOME (or XP Pro when set for simple file sharing) which only allows
authentication for shares through the guest account.

What I meant was many times a week, one of the users will be unable to
access
the data folder on the "server" machine. To solve that problem, we
usually
have
to shut down the "server" machine and all the users and then restart the
"server"
and after is is up, restart the users. That works even if it sometimes
takes several
tries.

This question of why the connections are lost remains the core problem. Are
your machines connected by a switch? A router? Any DHCP server running?
If not, static IPs or AIPA 169 addresses?
When the connection to share is lost is network functionality otherwise
still functional? Can you ping the server machine?

Yes, we just bought a new computer with xp home and were going to replace
the
old w2k "server" machine. I could never get the users to connect to the
xp
home

I guess that's a moot point now.

Thanks GTS for all of your wonderful info and help and insights!!!

You're very welcome.

 

[Kurt]

And as far as putting server software on the server machine, doesn't that

wipe away the current OS?? Or does it sit as an application on the
current OS???

Windows Server 2003 is the OS, replacing the Windows 2000 Pro OS you now
have installed. You cannot upgrade from a workstation OS to a server OS,
you'll need to reformat and do a clean install, then promote the new server
to a domain controller. You'll need to have a fully functional DNS server
(which can be set up for you by the OS installer), and all of your
workstations (which must be 2000 pro or XP pro) must have their DNS settings
pointing to the new server. In fact the server must point to itself for DNS
resolution (you should do that BEFORE you promote it to a DC). Then, you can
join the workstations to the new domain. User accounts must be created and
any permissions aside from the defaults can be assigned. Then users can log
into the new domain. You should take a look at the "File and Settings
Transfer Wizard" that comes on the XP Pro CD for a quick and easy way to get
the user's settings (desktop, favorites, My Documents, Outlook / Outlook
Express settings, etc) transferred from their old local accounts to their
new domain accounts. A Server OS (I suggest Windows 2003 Standard unless you
need exchange / SQL) costs about $600 to $700 US including 5 Client Access
Licenses (CALS). Additional licenses vary in price depending on where you
buy them, but are generally about $100 to $120 each (5 packs for around
$400). There are different licensing modes, but if you never have more than
5 users connecting to the server at any one time, the default "per server"
licensing should be fine. You should NEVER, EVER use your server as a
workstation - No Way, No How! It should stay as pristine as possible. And
finally, you should NOT attempt this for the first time in a production
environment. Set up a test network with a server and a couple of old
workstations and use it as a lab while you read a good book or two on the
subject.

....Kurt

 

[marsha]

That's the right thing to do for Win 2K. I

Sorry to be slow but what do you mean by "That's" the right thing to do???
Which is the right thing to do?

This question of why the connections are lost remains the core problem. Are
your machines connected by a switch? A router? Any DHCP server running?
If not, static IPs or AIPA 169 addresses?
When the connection to share is lost is network functionality otherwise
still functional? Can you ping the server machine?

All of the users connect to a D-Link smartswitch DSS 8 or 12? Anyway,
because
the wiring was screwed up big time due to terrible building situation, the
output of that
D-Link smartswitch goes to another D-Link DSS5 which connects to DSL modem
and
"server" computer. I have worried about the two DSS switches and figured
that was part
of the problem. The DSL modem is a Westell 2200 I think.

Gosh, I should know about static IPs but we never have a problem with DSL
and so it
has been so long that I have looked at it that I forget. But usually
business DSL in our
area is static. But I can't say ours is for sure. Like I say, we never
have a problem with
DSL.

Thanks!!!!!!!!!!!!!!!!!!!!!!!!

 

[marsha]

You'll need to have a fully functional DNS server

(which can be set up for you by the OS installer), and all of your
workstations (which must be 2000 pro or XP pro) must have their DNS settings
pointing to the new server. In fact the server must point to itself for DNS
resolution (you should do that BEFORE you promote it to a DC). Then, you can
join the workstations to the new domain.

I wasn't intending to set up the Domain thing. I was going to use the
server just the
same way we are doing but by using the server get a OS that is tuned for
concurrent
connections.

Does that make sense???

 

[GTS]

Sorry to be slow but what do you mean by "That's" the right thing to do???
Which is the right thing to do?

I was referring to your question about creating matchining users on the W2K
machine. That is appropriate.

All of the users connect to a D-Link smartswitch DSS 8 or 12? Anyway,
because
the wiring was screwed up big time due to terrible building situation, the
output of that
D-Link smartswitch goes to another D-Link DSS5 which connects to DSL modem
and
"server" computer. I have worried about the two DSS switches and figured
that was part
of the problem. The DSL modem is a Westell 2200 I think.

Gosh, I should know about static IPs but we never have a problem with DSL
and so it
has been so long that I have looked at it that I forget. But usually
business DSL in our
area is static. But I can't say ours is for sure. Like I say, we never
have a problem with
DSL.

Two switches shouldn't cause a problem. If you never have a problem with
Internet connectivity at the workstations, then I'm probably on the wrong
track in speculating that the share problem is due to connection glitches.
I take it your server has 2 NICs and is running ICS?

 

[marsha]

Two switches shouldn't cause a problem.

That is good to know. Thanks!

If you never have a problem with
Internet connectivity at the workstations, then I'm probably on the wrong
track in speculating that the share problem is due to connection glitches.

Correct, never had a problem with the individual users connecting to the
internet.
That is the first thing I check when a user has some problem connecting with
"server".
When I see that they can get on the internet, I know that the connection is
working
from them through both switches and hence to the "server".

I take it your server has 2 NICs and is running ICS?

No, the server, uses only one NIC and connects to that second switch as I
have
said. So while the server is only important to the LAN, the individual
users can use
the LAN to share the internet connection. For that matter the server can
also get
out on the internet since it has had a regular OS (w2k). But I don't like
for them to
use the server to get out on the internet due to the usual concerns.

As for ICS, I just set up a share network. I have dealt with ICS in the
past but I am
brain weary at the moment and don't think I have that setup at the office.
I know I
should be able to state definitively but I really don't think so.

 

[Kurt]

Yes. You can use the server in a workgroup. Pricing is the same whether you
use it as domain controller or not. You'll need a license for each
concurrent connection.

....kurt

 

[Kurt]

Also, if you want to use a server without promoting it to a DC, do NOT buy
the "small business" version.

....kurt

 

[marsha]

Yes. You can use the server in a workgroup. Pricing is the same whether you
use it as domain controller or not. You'll need a license for each
concurrent connection.

I just finished installing the demo of Windows 2003 Enterprise R2. I will
take it with me Monday and when things
are slow (the boss is gone so it will be a miracle if people even show up
I will substitute it for the "server" machine.
I am now a whiz at remapping on the users and I will probably shut down all
the users but one and try it with that one.

Thanks so much for you help!!! I'll let you know how it goes!!!

 

[marsha]

Also, if you want to use a server without promoting it to a DC, do NOT buy
the "small business" version.

Thanks much for that info!!!!