Error message: The server is not configured for transactions

Hello.

Windows 2003 server, domain controller, DNS, Statics IP's, only one DC on
network.

This is a new installation. All logons and browsing previously worked fine.

Now, when a client attempts to logon to the network, the message appears
that the roaming profile cannot be located. When trying to browse the
network, the message appears: (Domain) is not accessible. The server is not
configured for transactions.

The latter message started appearing intermittently as I was setting up home
folders and profile locations in the user accounts properties dialogue box. I
was trying different settings using a workstation to test the settings as I
was changing them. At the time, the workstation was logged on to the domain
fine. I first lost connectivity to the shared folders on the server. I then
pinged the server from the workstation, then I could connect to the shared
folders. Then being able to connect and not connect went back and forth a few
times. I was able to access the server and shared folders, then I wouldn't be
able to. Now I cannot connect at all. I have rebooted the server with no
success.

I can log on to the server using remote desktop and can administer the
server fine. DNS is working fine.Any help would be appreciated.
kt

you may have a virus. this case study may help,

server is not configured for transactions Case Study - Server is not configured for transactions. Situation: The client receives the following message error in a windows XP when attempting to map a ...
www.howtonetworking.com/casestudy/virus1.htm


Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
"KT" <(E-Mail Removed)> wrote in message news:65B5BFC5-831C-4271-984E-(E-Mail Removed)...
Hello.

Windows 2003 server, domain controller, DNS, Statics IP's, only one DC on
network.

This is a new installation. All logons and browsing previously worked fine.

Now, when a client attempts to logon to the network, the message appears
that the roaming profile cannot be located. When trying to browse the
network, the message appears: (Domain) is not accessible. The server is not
configured for transactions.

The latter message started appearing intermittently as I was setting up home
folders and profile locations in the user accounts properties dialogue box. I
was trying different settings using a workstation to test the settings as I
was changing them. At the time, the workstation was logged on to the domain
fine. I first lost connectivity to the shared folders on the server. I then
pinged the server from the workstation, then I could connect to the shared
folders. Then being able to connect and not connect went back and forth a few
times. I was able to access the server and shared folders, then I wouldn't be
able to. Now I cannot connect at all. I have rebooted the server with no
success.

I can log on to the server using remote desktop and can administer the
server fine. DNS is working fine.Any help would be appreciated.
kt