Cannot see domain server

[susantha silva]

Hi All,

Recently we delivered 2 new pc's to customer and I remotely networked them
to his exciting network He is having windows 2003 SBS server installed as
*****.local in his network but his previous 2 computers connected to the
network through a workgroup name. They all have a mapped network drive in
their computers which is belong to the server. When I checked in the network
palces in their computers I cannot see the server But still they have a
shared map drive. So I tried to add the 2 new computers to the domain
couldn't so ended up adding them to the workgroup. Then I mapped the sever
shared folder connecting to it using the ip address. But my main problem is
I've to enter the username and the password everytime I logged into the
machine in order to use the mapped drive. It don't even give the option to
save the password. Is their anyway to keep the mapped drive in the 2 new
computers without asking the password always?

 

[GTS]

You're post is a little confusing. If these are XP PRO machines mapping
shares on the 2003 server the solution would be to turn off simple file
sharing (if enabled) and create accounts on the server with usernames and
passwords matched to the workstations. Joining them to the domain and
managing this by domain user rights on the share would be a better solution,
but you give no indication of what the problem was with that, so can't
advise.

 

[Chuck]

Hi All,

Recently we delivered 2 new pc's to customer and I remotely networked them
to his exciting network He is having windows 2003 SBS server installed as
*****.local in his network but his previous 2 computers connected to the
network through a workgroup name. They all have a mapped network drive in
their computers which is belong to the server. When I checked in the network
palces in their computers I cannot see the server But still they have a
shared map drive. So I tried to add the 2 new computers to the domain
couldn't so ended up adding them to the workgroup. Then I mapped the sever
shared folder connecting to it using the ip address. But my main problem is
I've to enter the username and the password everytime I logged into the
machine in order to use the mapped drive. It don't even give the option to
save the password. Is their anyway to keep the mapped drive in the 2 new
computers without asking the password always?

Susantha,

Are the clients and the server setup properly?
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
# Ensure that the 2000 / XP clients are all configured to use the domain DNS
server. If you're using DHCP on your LAN, the DHCP server should provide the
domain DNS server address.
# Check Properties for the DNS server Forward Lookup Zone defined.
* On the General tab, ensure the domain DNS server is configured to permit
dynamic updates.
* On the Name Servers tab, ensure the DNS server points to itself as a DNS
server.
# Check Properties for the DNS server itself. For proper internet address
resolution, specify your ISP's DNS server(s) not on the individual clients, or
on the DHCP server, but in the Forwarders tab of the DNS server.

If you setup the clients as workgroup members, you have to synchronise passwords
on the clients and the server, so see if you can get the clients setup as domain
members.

 

[susantha silva]

Hi All,

Well sorry sor making a confusing question. But I'm also confused in here
I saw in their server 2 accounts are created that is exactly the names used
by the old computers. But they are not connected to the domain. I mena they
only have workgroup name not domain name. So I'm confused in here. So what
I'm thinking about creating 2 another user accounts in the server and used
the 2 new computers to join them. The main thing I see is whoever the person
setup the server has not taken teh full benifit of the server. Because if he
had then he should create user accounts and connect the clients to the
domain but instead he just created 2 user accounts in the server but 2
client machines are only connected with a workgroup name. So this is teh
confusing part to me. So which option is best for me? to make 2 accounts in
the server and conenct the 2 computers to the domain? If that so I think
I'll have to do it for the all 4 computers.

 

[Chuck]

Hi All,

Well sorry sor making a confusing question. But I'm also confused in here
I saw in their server 2 accounts are created that is exactly the names used
by the old computers. But they are not connected to the domain. I mena they
only have workgroup name not domain name. So I'm confused in here. So what
I'm thinking about creating 2 another user accounts in the server and used
the 2 new computers to join them. The main thing I see is whoever the person
setup the server has not taken teh full benifit of the server. Because if he
had then he should create user accounts and connect the clients to the
domain but instead he just created 2 user accounts in the server but 2
client machines are only connected with a workgroup name. So this is teh
confusing part to me. So which option is best for me? to make 2 accounts in
the server and conenct the 2 computers to the domain? If that so I think
I'll have to do it for the all 4 computers.

Susantha,

Whether to use a domain or workgroup is a question that should be asked by you
and by the customer.

A domain requires more work up front, but can be more secure and is easier to
maintain securely. A workgroup is easy to setup initially, but to make changes
in a workgroup requires more work. As you add computers, or employees come and
go, a workgroup is exponentially more work to maintain.

The customer paid for Server 2003, and apparently for a domain. I guess it's a
question of business ethics, and maybe legal responsibility if you can, and
should, provide a working domain.