domain name/setup w/ConnComp/XP PRo client PC locked out

From: Bob C (C_at_discussions.microsoft.com)
Date: 03/07/05 

Date: Mon, 7 Mar 2005 10:15:02 -0800

Folks........HELP !!!

I'm new to SBS 2003 and networks (from an admin & setup standpoint....I have
a general understanding and have read and re-read the "How to Cheat at Small
Business Server 2003" by Susan Snedaker).

I did a semi-clean install on a HP ML110 Server. I puchased it new from HP,
but the pre-loaded SBS seemed to have several things missing. I proceeded to
do a re-install of the SBS software when I saw alot of errors in the events
logs relating to "Bnd errors" and the booting process was taking longr and
longer each time.

Server has 2 NICS installed, but we use only 1.

My DSL modem (set in bridged mode) runs to a NetGear router (FR114P). We use
SBCGLOBAL as our ISP and use PPPoE with the router handling the verification.
I am using the NetGEar unit as the firewall.

After reading books and studying all your responses, I was able to get the
server setup, have it access the web & my email account and download all the
latest SBS 2003 fixes & patches.

One thing I remember during the setup was when I created my domain name, the
setup wizard flagged it being longer than 15 characters. I had read this was
only a problem with NETBIOS & older OS's. Since all our clients will be XP
Pro, I told the setup wizard it was ok.

After setup, I seethe domain name on the server as the long name I entered.

I later noticed the TCP/IP setting for the server had the "NetBIOS" switch
turned on. I removed this and re-booted the server.

Setup seemed to run ok.

When I log on as an administrtor, I noticed the network name was trunctaed
to 15 characters.

I created my first user id & client computer ok. I am able to logon to the
server using the user id & PW I created.

When I plugged the client into the NetGear router, I went to IE (as the
setup wizard instructed) and type the "ConnectComputer" command. I used the
domain name that was the "full name", meaning it was longer than the 15
characters that SBS flagged in the initial setup.

My 1st client is an XP Pro PC. The client was logged on as an administrator
and I had shut off Zone Alarm firewall & McAfee Virus scanner, just in case
it might try to block anything.

The client prompted me for my user id & password. Everything seemed to go ok.

I seemed to connect to the server, the server pushed some software down to
the client and the client eventually re-booted.

The first thing that comes up is the network logon screen. My user id was
filled in, as was the 2 options for connecting. One to the network (with the
15 character name) and the other being my computer.

When I try and logon to the network, it says the domain name is not found.
Worst, when I try to logon to my computer, it also says that name is not
found. Right now, the client is dead.

I cannot logon/turn on the client any way. My "recovery CD" from Dell gives
me 3 options, one to re-install XP Home (I purchased a XP Pro upgrade), or to
logon on as an administrator. The third option is to exit. Great !!!

When I proceed to logon the client as an administrator from a DOS promt,
using the admin PW I have been using, it says it cannot be found. Best I can
do is enter nothing and it shows me about 25 DOS commands I can use from the
DOS promt.

Needless to say, I'm stuck. I was making alot of progress with this, bu
having the client shot at this point is a huge problem.

Having these domain name issues is another thing. Why SBS would allow me to
create a domain name greater than 15 characters seems strange is you haven't
gotten to the NETBIOS switch at that point.

Needless to say, any help is greatly appreciated.

Bob

Relevant Pages

  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.exchange2000.general)
  • Cant delegate/share to a group
    ... I am running Exchange 2000 SP3 on SBS 2000 on a network with one server box. ... The client operation failed". ... Successful Network Logon: ...
    (microsoft.public.backoffice.smallbiz2000)
  • 802.1X Setup using Server 03 and Aironet 1200 Series WAP help
    ... I'd really appreciate some direction as I tried to setup a Cisco 1242 ... Series WAP as a Radius Client with 802.1x authentication on a Windows ... Server 2003 R2 DC running IAS/RADIUS,DNS,DHCP. ...
    (microsoft.public.internet.radius)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • Re: Network Connection
    ... For the clients make sure that you use following policy to prevent logon with cached credentials: ... Additional post an unedited ipconfig /all from the DC/DNS server and a problem machine so we can exclude DNS configuration problems. ... From last December I have been experiencing network connection problem ... out client pc some with Vista and the rest with XP. ...
    (microsoft.public.windows.server.networking)