Jump to content

Free help from tech experts
Welcome to Geeks to Go forums. Create a FREE account now to gain access to all our features. Once registered and logged in, you will be able to create topics, post replies to existing topics, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. Best of all, registration and all assistance is 100% free! This message, and all ads will be removed once you sign in.
Create an Account Login to Account

Net Use \\ComputerName sysem error 5


  • Please log in to reply

#1
docfxit

docfxit

    Member

  • Member
  • PipPip
  • 94 posts
Hi,

When I try to connect to a network share it asks me for a user name and password. When I put in the user name and password it asks me for the user name and password again. I have the exact same user name and password in both machines.

When I try on a cmd line net use \\ComputerName ( I use the actual computer name) it gives me an error:
System error 5

Access denied.

I found an MS article that said to make sure Net Logon service was started. When I start the service it gives me a window saying:
"The Net Logon service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."


This PC is XP Pro sp2. And this has worked with the same netshare before.

I tried mapping a network drive on a pc that never had it working before. I'm getting the same error. Also XP Pro. sp2

I tried connecting to the same share from a '98se pc. It worked fine.
I tried connecting to the same share from a Ubuntu pc. It worked fine.

Could someone please help me figure out what is wrong with the first two machines?

Thank you,

Docfxit

Edited by docfxit, 15 January 2011 - 12:41 AM.

  • 0

Similar Topics: Net Use \\ComputerName sysem error 5     x


#2
Artellos

Artellos

    Tech Secretary

  • Global Moderator
  • 3,876 posts
Could you provide me with an IPConfig log of each machine?

  • Go to Start and open Run.
  • In the Box, type in cmd
  • A black box will appear. Type in: ipconfig /all
  • A lot of information will appear, Please right click the black window and hit Select All.
  • Hit Enter to copy.
  • Then paste it into your next reply.

Regards,
Olrik
  • 0

#3
docfxit

docfxit

    Member

  • Member
  • PipPip
  • 94 posts
This XP Pro PC won't connect to scans share.
Host Name . . . . . . . . . . . . : ScanStation1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® 82566DM Gigabit Network Connection
Physical Address. . . . . . . . . : 00-1A-6B-4C-EF-E8
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 66.51.205.100
66.51.206.100

This XP Pro PC won't connect to scans share.
Host Name . . . . . . . . . . . . : ATUUser4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Express Adapter
Physical Address. . . . . . . . . : 00-16-CF-19-C7-32

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-16-36-4D-19-22
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 66.51.205.100
66.51.206.100

This 98 PC will connect to scans share. If I use \\atu1277\scans
Host Name . . . . . . . . . : jim.
DNS Servers . . . . . . . . : 66.218.44.5
66.218.44.90
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : Yes

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : 00-50-DA-B7-CD-68
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 192.168.1.254
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . :
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

2 Ethernet adapter :

Description . . . . . . . . : Kingston EtheRx KNE111TX PCI Fast Ethernet Adapter
Physical Address. . . . . . : 00-C0-F0-75-07-D8
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 208.127.xxx.xxx
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 208.127.xxx.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :
I see I need to change the DNS on this PC. When I get into the office I will do that.

Thank you for looking at this.

Docfxit
  • 0

#4
Artellos

Artellos

    Tech Secretary

  • Global Moderator
  • 3,876 posts
On each of the PCs, try these commands;
  • Go to Start and select Run.
  • In the Box, type cmd
  • A black box will appear. Execute these commands from top to bottom.

    ping 192.168.1.23
    ping 192.168.1.4
    ping 192.168.1.254

  • A lot of information will appear, Please right click the black window and select all.
  • Hit Enter to copy the text.
  • Then paste it into your next reply.

Regards,
Olrik
  • 0

#5
docfxit

docfxit

    Member

  • Member
  • PipPip
  • 94 posts
On ScanStation1 at 192.168.1.23

Pinging 192.168.1.23 with 32 bytes of data:

Reply from 192.168.1.23: bytes=32 time<1ms TTL=128
Reply from 192.168.1.23: bytes=32 time<1ms TTL=128
Reply from 192.168.1.23: bytes=32 time<1ms TTL=128
Reply from 192.168.1.23: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.4 with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=128
Reply from 192.168.1.254: bytes=32 time<1ms TTL=128
Reply from 192.168.1.254: bytes=32 time<1ms TTL=128
Reply from 192.168.1.254: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=53ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 53ms, Average = 14ms

From ATUUser4 192.168.1.4

Pinging 192.168.1.23 with 32 bytes of data:

Reply from 192.168.1.23: bytes=32 time<1ms TTL=128
Reply from 192.168.1.23: bytes=32 time<1ms TTL=128
Reply from 192.168.1.23: bytes=32 time<1ms TTL=128
Reply from 192.168.1.23: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.4 with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=128
Reply from 192.168.1.254: bytes=32 time<1ms TTL=128
Reply from 192.168.1.254: bytes=32 time<1ms TTL=128
Reply from 192.168.1.254: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

From jim.at 192.168.1.254

Pinging 192.168.1.23 with 32 bytes of data:

Reply from 192.168.1.23: bytes=32 time=1ms TTL=128
Reply from 192.168.1.23: bytes=32 time<10ms TTL=128
Reply from 192.168.1.23: bytes=32 time<10ms TTL=128
Reply from 192.168.1.23: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

Pinging 192.168.1.4 with 32 bytes of data:

Reply from 192.168.1.4: bytes=32 time=1ms TTL=128
Reply from 192.168.1.4: bytes=32 time<10ms TTL=128
Reply from 192.168.1.4: bytes=32 time<10ms TTL=128
Reply from 192.168.1.4: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<10ms TTL=128
Reply from 192.168.1.254: bytes=32 time<10ms TTL=128
Reply from 192.168.1.254: bytes=32 time<10ms TTL=128
Reply from 192.168.1.254: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=65ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 65ms, Average = 18ms

From ATU1277 at 192.168.1.1
Verifying connection to host system 192.168.1.23.
PING reply 1 from 192.168.1.23 took 13 ms. 256 bytes. TTL 128.
PING reply 2 from 192.168.1.23 took 4 ms. 256 bytes. TTL 128.
PING reply 3 from 192.168.1.23 took 4 ms. 256 bytes. TTL 128.
PING reply 4 from 192.168.1.23 took 4 ms. 256 bytes. TTL 128.
PING reply 5 from 192.168.1.23 took 4 ms. 256 bytes. TTL 128.
Round-trip (in milliseconds) min/avg/max = 4/5/13
Connection verification statistics: 5 of 5 successful (100 %).

Verifying connection to host system 192.168.1.4.
PING reply 1 from 192.168.1.4 took 5 ms. 256 bytes. TTL 128.
PING reply 2 from 192.168.1.4 took 4 ms. 256 bytes. TTL 128.
PING reply 3 from 192.168.1.4 took 4 ms. 256 bytes. TTL 128.
PING reply 4 from 192.168.1.4 took 4 ms. 256 bytes. TTL 128.
PING reply 5 from 192.168.1.4 took 4 ms. 256 bytes. TTL 128.
Round-trip (in milliseconds) min/avg/max = 4/4/5
Connection verification statistics: 5 of 5 successful (100 %).

Verifying connection to host system 192.168.1.254.
PING reply 1 from 192.168.1.254 took 4 ms. 256 bytes. TTL 128.
PING reply 2 from 192.168.1.254 took 4 ms. 256 bytes. TTL 128.
PING reply 3 from 192.168.1.254 took 4 ms. 256 bytes. TTL 128.
PING reply 4 from 192.168.1.254 took 4 ms. 256 bytes. TTL 128.
PING reply 5 from 192.168.1.254 took 4 ms. 256 bytes. TTL 128.
Round-trip (in milliseconds) min/avg/max = 4/4/4
Connection verification statistics: 5 of 5 successful (100 %).

Verifying connection to host system 192.168.1.1.
PING reply 1 from 192.168.1.1 took 2 ms. 256 bytes. TTL 64.
PING reply 2 from 192.168.1.1 took 1 ms. 256 bytes. TTL 64.
PING reply 3 from 192.168.1.1 took 1 ms. 256 bytes. TTL 64.
PING reply 4 from 192.168.1.1 took 1 ms. 256 bytes. TTL 64.
PING reply 5 from 192.168.1.1 took 1 ms. 256 bytes. TTL 64.
Round-trip (in milliseconds) min/avg/max = 1/1/2
Connection verification statistics: 5 of 5 successful (100 %).


I included 192.168.1.1 because that machine is where the shared folder is.

Thanks,

Docfxit
  • 0

#6
docfxit

docfxit

    Member

  • Member
  • PipPip
  • 94 posts
When I do a net view on the scanstation1 I see:
Server Name Remark

-------------------------------------
\\ATU1277 ATU1277
\\ATUUSER11
\\ATUUSER4 Laptop
\\SCANSTATION1
\\UBUNTU Samba 3.0.26a
The command completed successfully.

Which looks correct to me.

If I do a nbtstat -a atu1277

Local Area Connection:
Node IpAddress: [192.168.1.23] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
ATU1277 <20> UNIQUE Registered

MAC Address = 00-00-00-00-00-00

It doesn't show the correct IP address. It should be 192.168.1.1 for atu1277
The scanstation1 is 192.168.1.23
It doesn't show that it's part of Workgroup.
It shows the wrong MAC address.

If I purge the name cache and reload it:
nbtstat -r

NetBIOS Names Resolution and Registration Statistics
----------------------------------------------------

Resolved By Broadcast = 6
Resolved By Name Server = 0

Registered By Broadcast = 5
Registered By Name Server = 0

NetBIOS Names Resolved By Broadcast
---------------------------------------------
UBUNTU
UBUNTU <00>
UBUNTU
WORKGROUP <1D>
UBUNTU <00>
UBUNTU

I don't understand why it doesn't find all the other PC's on the LAN.

If I list the contents of the NetBIOS name cache:
nbtstat -c

Local Area Connection:
Node IpAddress: [192.168.1.23] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]
------------------------------------------------------------
UBUNTU <20> UNIQUE 192.168.1.101 35
ATU1277 <03> UNIQUE 192.168.1.1 -1
ATU1277 <00> UNIQUE 192.168.1.1 -1
ATU1277 <20> UNIQUE 192.168.1.1 -1
ATU1277.COM <03> UNIQUE 192.168.1.1 -1
ATU1277.COM <00> UNIQUE 192.168.1.1 -1
ATU1277.COM <20> UNIQUE 192.168.1.1 -1

I don't understand why ATU1277 and ATU1277.com is in there so many times.

How can I fix this?

Thanks,

Docfxit
  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

featured