Troubleshooting netbios/tcpip NET USE from DOS

  • Thread starter Thread starter BertieBigBollox
  • Start date Start date
B

BertieBigBollox

Got a Windows 2000 server that is the PDC. Got a user called PXE
created on here.

Trying to boot a laptop from floppy and then access a share on the
windows 2000 server. Trouble is I'm getting the message

'You have been logged, but have not been validated by a server.
Therefore, you may not have permission to use some network resources.'

I can ping the server from laptop so thats OK but how do I start
troubleshooting this?
 
Got a Windows 2000 server that is the PDC. Got a user called PXE
created on here.

Trying to boot a laptop from floppy and then access a share on the
windows 2000 server. Trouble is I'm getting the message

'You have been logged, but have not been validated by a server.
Therefore, you may not have permission to use some network resources.'

I can ping the server from laptop so thats OK but how do I start
troubleshooting this?

You probably need to have the NetBEUI protocol installed on the Windows
2000 server. Take a look at the LANA0= line in the protocol.ini file on
the floppy diskette.

John
 
Hello John John - MVP,

If i remember correct this message belongs to security configuration, check
your domain controller GPO for:
Domain member: Digitally encrypt or sign secure channel data (always) - Disabled

Microsoft network client: Digitally sign communications (always) - Disabled
Microsoft network server: Digitally sign communications (always) - Disabled
Network security: LAN Manager authentication level - Send LM & NTLM responses


We used DOS bootdisk some time ago and never used NetBEUI.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
You probably need to have the NetBEUI protocol installed on the Windows
2000 server.  Take a look at the LANA0= line in the protocol.ini fileon
the floppy diskette.

John

Thing is I'm sure this was working on a similarly configured server so
i dont think theres a great deal wrong. Certainly both servers are
identical in terms of software installed.

Do you mean under network settings/advanced /enable netbeui?
 
More info. I can ping the server in question from DOS (from the dos
booted laptop).

NET VIEW returns nothing. NET VIEW \\servername returns an error as
does NET VIEW \\ipaddress.

NET USE X: \\ipaddress\sharename also fails.
 
Thing is I'm sure this was working on a similarly configured server so
i dont think theres a great deal wrong. Certainly both servers are
identical in terms of software installed.

Do you mean under network settings/advanced /enable netbeui?

Did you verify the settings given by Meinolf?

I mean to install the NetBEUI protocol at the adapter, right click on
the adapter and select Properties and then click on install to install
the protocol.

John
 
message
Got a Windows 2000 server that is the PDC. Got a user called PXE
created on here.

Trying to boot a laptop from floppy and then access a share on the
windows 2000 server. Trouble is I'm getting the message

'You have been logged, but have not been validated by a server.
Therefore, you may not have permission to use some network
resources.'

This message is always generated when you use NET LOGON with the DOS
client. It is just an informational message, and does not necessarily
mean you cannot access network resources but it also does not mean you
CAN. You can safely ignore it.
I can ping the server from laptop so thats OK but how do I start
troubleshooting this?

From one of your other messages, you indicate that NET USE fails, can
you give the exact error message?

While you are at it, the entire NET LOGON command would be useful -
specifically, are you including the /DOMAIN:domainname parameter? If
not, do so and reply back with the results. I think it can also be
specified in SYSTEM.INI in the [network] section with a
logondomain=domainname setting, so the contents of your SYSTEM.INI
might be useful as well.

FYI, I use the DOS client extensively in my environment, but never in
a Windows Domain setting. NET LOGON /? indicates it can be used in a
Windows NT or LAN Manager domain, but we use an Active Directory
domain based on Windows Server 2008 and I've never been able to get
access to domain resources, but I can access non-domain resources.
I've never used NetBEUI, but as far as I know it isn't required.

--
Zaphod

Arthur Dent, speaking to Trillian about Zaphod:
"So, two heads is what does it for a girl?"
"...Anything else he's got two of?"
 
Hello Zaphod,

What you see is expected behaviour. Since Windows server 2003 the SMB signing
and also the domain security settings are increased. That resulted in the
not working DOS bootdisk's. You have to use a BartPe or equivalent start
disk to connect to a domain.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

message
..
Got a Windows 2000 server that is the PDC. Got a user called PXE
created on here.

Trying to boot a laptop from floppy and then access a share on the
windows 2000 server. Trouble is I'm getting the message

'You have been logged, but have not been validated by a server.
Therefore, you may not have permission to use some network
resources.'
This message is always generated when you use NET LOGON with the DOS
client. It is just an informational message, and does not necessarily
mean you cannot access network resources but it also does not mean you
CAN. You can safely ignore it.
I can ping the server from laptop so thats OK but how do I start
troubleshooting this?
From one of your other messages, you indicate that NET USE fails, can
you give the exact error message?

While you are at it, the entire NET LOGON command would be useful -
specifically, are you including the /DOMAIN:domainname parameter? If
not, do so and reply back with the results. I think it can also be
specified in SYSTEM.INI in the [network] section with a
logondomain=domainname setting, so the contents of your SYSTEM.INI
might be useful as well.

FYI, I use the DOS client extensively in my environment, but never in
a Windows Domain setting. NET LOGON /? indicates it can be used in a
Windows NT or LAN Manager domain, but we use an Active Directory
domain based on Windows Server 2008 and I've never been able to get
access to domain resources, but I can access non-domain resources.
I've never used NetBEUI, but as far as I know it isn't required.

Arthur Dent, speaking to Trillian about Zaphod:
"So, two heads is what does it for a girl?"
"...Anything else he's got two of?
 
Hello Zaphod,

What you see is expected behaviour. Since Windows server 2003 the SMB signing
and also the domain security settings are increased. That resulted in the
not working DOS bootdisk's. You have to use a BartPe or equivalent start
disk to connect to a domain.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm


message
..
This message is always generated when you use NET LOGON with the DOS
client.  It is just an informational message, and does not necessarily
mean you cannot access network resources but it also does not mean you
CAN.  You can safely ignore it.
From one of your other messages, you indicate that NET USE fails, can
you give the exact error message?
While you are at it, the entire NET LOGON command would be useful -
specifically, are you including the /DOMAIN:domainname parameter?  If
not, do so and reply back with the results.  I think it can also be
specified in SYSTEM.INI in the [network] section with a
logondomain=domainname setting, so the contents of your SYSTEM.INI
might be useful as well.
FYI, I use the DOS client extensively in my environment, but never in
a Windows Domain setting.  NET LOGON /? indicates it can be used in a
Windows NT or LAN Manager domain, but we use an Active Directory
domain based on Windows Server 2008 and I've never been able to get
access to domain resources, but I can access non-domain resources.
I've never used NetBEUI, but as far as I know it isn't required.
Arthur Dent, speaking to Trillian about Zaphod:
"So, two heads is what does it for a girl?"
"...Anything else he's got two of?"- Hide quoted text -

- Show quoted text -

Windows 2000 server....
 
Meinolf Weber said:
message
..
Got a Windows 2000 server that is the PDC. Got a user called PXE
created on here.

Trying to boot a laptop from floppy and then access a share on the
windows 2000 server. Trouble is I'm getting the message

'You have been logged, but have not been validated by a server.
Therefore, you may not have permission to use some network
resources.'
This message is always generated when you use NET LOGON with the
DOS
client. It is just an informational message, and does not
necessarily
mean you cannot access network resources but it also does not mean
you
CAN. You can safely ignore it.
I can ping the server from laptop so thats OK but how do I start
troubleshooting this?
From one of your other messages, you indicate that NET USE fails,
can
you give the exact error message?

While you are at it, the entire NET LOGON command would be useful -
specifically, are you including the /DOMAIN:domainname parameter?
If
not, do so and reply back with the results. I think it can also be
specified in SYSTEM.INI in the [network] section with a
logondomain=domainname setting, so the contents of your SYSTEM.INI
might be useful as well.

FYI, I use the DOS client extensively in my environment, but never
in
a Windows Domain setting. NET LOGON /? indicates it can be used in
a
Windows NT or LAN Manager domain, but we use an Active Directory
domain based on Windows Server 2008 and I've never been able to get
access to domain resources, but I can access non-domain resources.
I've never used NetBEUI, but as far as I know it isn't required.
Hello Zaphod,

What you see is expected behaviour. Since Windows server 2003 the
SMB signing and also the domain security settings are increased.
That resulted in the not working DOS bootdisk's. You have to use a
BartPe or equivalent start disk to connect to a domain.

I suspected that was the case, and fortunately for our production
environment I don't need domain resources. What I do need is speed,
and the DOS boot disk approach is considerably faster than a BartPE or
other Windows PE based boot. Until I can no longer boot DOS and use a
DOS client I'll stick with that approach.

--
Zaphod

Arthur: All my life I've had this strange feeling that there's
something big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.
 
Back
Top