server not configured for transactions

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

i have two servers set up on a workgroup. neither of them are domain
controllers...both of them obtain internal ip addresses from a router. i
also have about ten workstations on the workgroup. if i go into network
places -> computers near me, both servers throw an error that says server not
configured for transactions.

More info: currently this is a really basic os setup. there is no
additional windows components on each server except DNS and whatever
necessary components might be automatically added by default. The only
programs installed on each machine are Ad-Aware on both and Goldmine
(database program) on one machine, neither of which access the network at
all.

Any suggestions would be helpful and very appreciative.
 
Workgroup machines can only connect to each other if they all have idencial
user accounts created on them with identical passwords. the workgroup "name"
must also match.
 
....granted, it may not solve the problem, but it creates a consistant
environment to work from...
 
That usually means the $ipc share is missing. You might be able to fix it by
using the " net share ipc$ " command or uninstalling and reinstalling file
and print sharing. Since this has happened on two computers I would be
concerned of a malware problem. Be sure to do full scan for parasite and
viruses using the latest up to date definitions for all the packages you
use. If problems are found you should determine what the vulnerability is,
such as no/improperly configured firewall, not current with critical
updates, weak passwords, etc. and take action to remedy or the problem will
probably reappear.--- Steve
 
This is only partially correct. While it is convenient if the workgroup
names match, there is no compelling need for them to be the same.
Machines belonging to different workgroups can access each other's
shares, provided that the account credentials match.


Phillip Windell said:
Workgroup machines can only connect to each other if they all have idencial
user accounts created on them with identical passwords. the workgroup "name"
must also match.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


km said:
i have two servers set up on a workgroup. neither of them are domain
controllers...both of them obtain internal ip addresses from a router. i
also have about ten workstations on the workgroup. if i go into network
places -> computers near me, both servers throw an error that says
Click to expand...
server
not
configured for transactions.

More info: currently this is a really basic os setup. there is no
additional windows components on each server except DNS and whatever
necessary components might be automatically added by default. The only
programs installed on each machine are Ad-Aware on both and Goldmine
(database program) on one machine, neither of which access the network at
all.

Any suggestions would be helpful and very appreciative.
Click to expand...
Click to expand...
 
Pegasus (MVP) said:
This is only partially correct. While it is convenient if the workgroup
names match, there is no compelling need for them to be the same.
Machines belonging to different workgroups can access each other's
shares, provided that the account credentials match.
Click to expand...

True. I guess I should have wored that a little better.
 
Back
Top