DOS logon Windows Server 2003

Hi Group!

I have a special problem with a norton ghost boot disc that uses a PC DOS
Version. I would like to logon on my domain with the command: net logon
/domain:HAK ...!

After that I would like to use a network share for ghost imaging. after the
net logon I get the following error message in German:

"Sie wurden angemeldet, aber nicht von einem Server bestätigt.
Möglicherweise haben Sie keine Berechtigung um einige der Netzwerkressourcen
zu benutzen."

That could be the following in English....

"You have been logged on but your logon has not been confirmed by a server.
Perhab you do not have the permission to use some network resources.." (free
translation)

I found that I have to disable SMB signing on my domain controllers - Well I
did but that did not help me. This disk works with a Windows2000 DC - so
there are no errors in the batches!

Anyone an idea what I could try (other DOS version..?). A solution could
help me save a lot of time when imaging computers!

best regards

andy

 

In

I've been using Ghost since v 2.d (1995). Usually disabling SMB signing will
do the trick with a 2003 domain, whether using MS DOS, or PC DOS.

How did you disable SMB signing?

--
Ace
Innovative IT Concepts, Inc
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

 

Hi Ace!

I disabled the policy in the "default domain controller policy" - that
should be the right way..?

best regards

andy

 

In

Yes, that's the way. Do you remember the name of the setting you disabled?

Here's the setting:

811497 - Error Message When Windows 95 or Windows NT 4.0 Client Logs On to
Windows Server 2003 Domain:
http://support.microsoft.com/?id=811497

I haven't used PC DOS. I've always used MS DOS. In know some guys that use
PC DOS without problems to 2003 DCs.

How exactly are you logging on? When I log on, I just specify the username
as say, administrator, then just type in the password. I don't specify the
domain name, it defaults to the domain's administrator account since on the
DOS side, if you do not specify any workgroup or domain in the system.ini
file, then it just defaults to the resource's domain or workgroup you are
connecting to.

Ace

 

Hi Ace!

We are using the following command to logon: (the user ghost has domain
admin rights!)

net logon ghost ghost /domain:HAK

The system then prompts for a password - we reenter ghost and then get the
error message i described!

best regards

andy

 

In

Just use

net logon ghost

then enter the password. Try that. Otherwise, try:

net logon ghost /domain:HAK

Also, post your system.ini file please.

Here's a reference guide for the net logon command:
http://www.geocities.com/rick_lively/MANUALS/COMMANDS/N/NETLOGON.HTM





Ace

 

Hi Aces - thanks for your answers - I will have my next tries on Wednesday
next week!

I hope I can post the system.ini file before as I do not have the start disk
now!

thanks

andy

 

Hi Ace!

Here is the content o system.ini:

[network]
computername=c61
filesharing=no
printsharing=no
autologon=yes
lanroot=k:\NET
username=ghost
workgroup=hak
reconnect=no
directhost=no
dospophotkey=N
lmlogon=0
logondomain=hak
preferredredir=full
autostart=full
maxconnections=20

[network drivers]
netcard=B57.dos
transport=ndishlp.sys,*netbeui
devdir=k:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=k:\net\Shares.PWL

GHOST=k:\NET\GHOST.PWL

 

In

Thanks for posting that!

HAK is already set as the workgroup, which it also looks at it as the domain
name too. SO you can just specifiy the username without the domain. I've
been doing that for years that way.

I see that you are using NetBEUI. Is that also installed on the server you
are trying to connect to? May I suggest to simplify it by using creating a
TCPIP bootable instead of using NetBEUI? NetBEUI is too much overhead on the
network. Even IPXSPX is better than NetBEUI.

Ace

 

Hi Ace!

Now I tried an bootdisk from www.netbootdisc.com and had the same error -
now in english:

"You were logged on but have not been validated by a server". Therfore you
may not have permission to use some network resources"

I also could see that there are no entries in the event log for logons - if
other users logon i can see entries - so I think there might go something
wrong with the logon process..

any further ideas - I will now also try in another domain!

cu

andy

 

In

What protocol are you using? I think the problem maybe using NetBEUI or
possibly in the protocol.ini file. I found one article talking about
ODI/NDIS issues wtih the same thing, but that was for IPX.

But according to the article below, it says to ignore the error and that you
got logged on anyway. Curious, have you tried to simply map a drive after
you get the message and change to that drive letter?

LAN Manager MS-DOS NET LOGON: LANAs and Validation
http://support.microsoft.com/default.aspx?scid=kb;en-us;98084

I would highly suggest to use TCP/IP for your bootable when connecting to
2003. It eliminate alot of the above issues and is also less overhead on
your server to run any additional protocols. I don't know what
netbootdisc.com has to offer in TCPIP, but I built my own custom 2.8meg
network bootable image that supports 45 different NICs that I burned to a CD
using Bart's Boot disks, which works great. It took me months of tweaking it
before I got it right. I suggest to take a look at Bart's site and his
methods. Read up on it and learn it. It's a great tool.
http://www.nu2.nu/bootdisk/network/

Let me know how you make out.

Ace

 

Hi Ace!

Many thanks for your answers - I am now on vacation for a week and will let
you know how we solved the problem!

best regards

andy

 

In

Enjoy!

 

Hello Ace

I'm having the same trouble as Andreas is, I have read the whole thread and
tried all your ideas, with no luck.

You are writting that you made your own boot cd, with 45 NIC drivers on it
and you can make it work with a Windows 2003 Server share.

Would you be so kind to share you boot cd?

Best Regards
Jesper Jensen