asked on

SBS 2003 Loses Connectivity after Userenv (1053) Errors.

A bit of background: My company's network is running SBS 2003 as a web application server (a setup that I inherited...) using IIS 6.0, ASP.net frontend with a SQL 2000 backend. We process all our transactions with this system.

After three to five hours of uptime error 1053 from userenv (Windows cannot determine user or computer name, the rpc server is unavailable. GP processing aborted) will come up and nobody will be able to connect to the website hosted on the machine, and when attempting to browse to any website, IE will just show "http:///"

The strange thing is, it can still browse to other machines on the network, and ping by hostname. It's pointed to itself as the DNS server. See below for the ipconfig/all from this server:

I've disabled offloading on the NIC and rolled back any recent updates. Also I've searched for hours, but cannot find anyone with the same symptoms....any suggestions?

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
 
C:\Documents and Settings\Administrator>ipconfig /all
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : HARVESTING
   Primary Dns Suffix  . . . . . . . : sevenislandsland.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : sevenislandsland.local
 
Ethernet adapter Local Area Connection 2:
 
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network Connection w
ith I/O Acceleration #4
   Physical Address. . . . . . . . . : 00-30-48-63-C6-07
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.5
   DNS Servers . . . . . . . . . . . : 192.168.1.2
                                       192.168.1.1
 
C:\Documents and Settings\Administrator>

Open in new window

suppsaws

Hello svaillancourt,

remove this dns server: 192.168.1.1
the ONLY dns server on an SBS (and also the clients) should be the SBS server itself.
rerun the CEICW and put any other external ISP dns server(s) in thAt wizard only.

Regards,

suppsaws

suppsaws

svaillancourt,

and btw, is this SBS server the ONLY dhcp server?

suppsaws

svaillancourt

ASKER

The setup is a bit strange, DHCP is not enabled. Its running on its own little (one machine) domain with a static IP address.

svaillancourt

ASKER

Also, I've done what you suggested in the first post, (made the only DNS server the address of the local machine.) Now time will tell.

suppsaws

it's normal that dhcp is not enabled, the SBS needs a fixed ip, but the SBS server should be the DHCP server, the clients should be on dhcp, provided by the SBS server, is that the case?

svaillancourt

ASKER

There are no clients. Its running as a stand-alone web server with no end user client machines.

suppsaws

hm, I wonder why you are using an SBS server since you are only using about 5% of the whole server.
AD is installed though, is it? what about exchange?

svaillancourt

ASKER

I'm wondering the same thing! heh .... its an inherited system from a predecessor. AD is installed. No exchange. And a big part of my troubleshooting this issue would be looking at the zones in DNS, however DNS is not listed under administrative tools.

ASKER CERTIFIED SOLUTION

suppsaws

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

svaillancourt

ASKER

Agreed. I installed/configured the other roles and it appears to be behaving now. But I really won't know for another three hours.

suppsaws

I guess you will bounce onto some more problems, because you also notice that that guy didn't know how to setup an sbs properly.
And, since this is sbs, everything is linked to oneother, but we'll see, we'll fix it :)

svaillancourt

ASKER

It is working now. :) I had to (re) install DNS, but after that. Not a hitch.

Thanks.