|
Post Number: 11
|
Wiley
©0®ÞØ®4+3 whØ®3
Group: Members
Posts: 1268
Joined: Oct. 2001
|
|
Posted on: Jun. 03 2002,02:00 |
|
|
9-->Quote (Rshias @ 02 June 2002,169) | From other systems on the network, the shared resources on the system in question can be accessed and mapped without a problem. |
Just to be clear, you can see the troubled computer in Network Places? Ok, so we know file sharing is on (Client for Microsoft Networks) and remote users have rights to the local problemed computer.
Quote | When on the troublesome one, nothing can be accessed from the network, and workgroup computers are not displayed. It's unable to "see" anyone else. It can ping outside systems fine, but can't do much more than that. |
So I'm assuming you've tried the net view \\computername and it came up empty. Yet you can ping it by name? Might as well try nbtstat -R just to try and purge and reload the name table ...don't think that will work though, there is something fishy with broadcasting the name.
Quote | Attempting to map drives from that system causes a "network path not found" error. Trying to access through the Run ability gives a: "This file does not have a program associated with this action. Create an association in the Folder Options control panel." |
Hmmm ....ok three steps to try.
1. Stop and restart the Computer Browser service under Control Panel/Admin Tools/Services ...this is most likely the cause of your problem, check event viewer for details after it starts.
2. Put this computer into a different workgroup and reboot this will force the computer to update it's browselist. If it works you can just switch the workgroup back.
3. Rename the computer ...it may be conflicting with another computer or itself.
Let me know if that worked
-------------- There's a sucker born every minute ...but swallowers are hard to find.
|
|
|
|
Post Number: 12
|
Rshias
The Insomniac
Group: Members
Posts: 198
Joined: Jan. 2001
|
|
Posted on: Jun. 03 2002,02:28 |
|
|
First quote:: Correct. Other computers can see and access the troubled one, but the troubled one can't see or access the others.
Second quote:: Net view works fine from the troubled system. It can also ping other systems by name.
Third quote:: Tried all three steps. No dice.
EDIT: The following are installed ~~~~~~~~~~~~~~~~~~~ Client for Microsoft Networks File and print sharing QoS packet scheduler TCP/IP
Edited by Rshias on Jan. 01 1970,01:00
-------------- Sleep is for the weak.
|
|
|
|
Post Number: 13
|
Wiley
©0®ÞØ®4+3 whØ®3
Group: Members
Posts: 1268
Joined: Oct. 2001
|
|
Posted on: Jun. 03 2002,04:21 |
|
|
Quote (Rshias @ 02 June 2002,18:28) | Second quote:: Net view works fine from the troubled system. It can also ping other systems by name. |
If net view works then you have to be able to map a remote share ...you're resolving the shares the exact same way ...just different views. From local messed up machine- net view \\remote_computer you see the share net use x: \\remote_computer\share you assign a drive letter to represent the remote share that you can see ...this has to work now, if you can map it and not open it that a different story. Double check the event viewer ...see if it is loggin anything about the browser service returning an error or the workstation service. ---work around--- create a file in c:\windows\system32\drivers\etc called lmhosts (it is important that there is no extention at the end of the file name ...there is usually an lmhosts file in that directory with a hidden extention of .sam ...create a blank file and use no extention) write this line in the new file and save (variables are in bold) 192.168.1.1 remote_computer_name #DOM:workgroup #PRE reboot help any? If not my guess is that the browser service is hosed ..but you should still be loging an error ...unless I'm missing something.
-------------- There's a sucker born every minute ...but swallowers are hard to find.
|
|
|
|
Post Number: 14
|
Rshias
The Insomniac
Group: Members
Posts: 198
Joined: Jan. 2001
|
|
Posted on: Jun. 03 2002,04:59 |
|
|
C:\DOCUME~1\ADMIN>cd \
C:\>ping computer27
Pinging Computer27 [10.0.1.27] with 32 bytes of data:
Reply from 10.0.1.27: bytes=32 time<1ms TTL=128 Reply from 10.0.1.27: bytes=32 time<1ms TTL=128 Reply from 10.0.1.27: bytes=32 time<1ms TTL=128 Reply from 10.0.1.27: bytes=32 time<1ms TTL=128
Ping statistics for 10.0.1.27: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>net view \\computer27 Shared resources at \\computer27
Computer27
Share name Type Used as Comment
------------------------------------------------------------------------------- E Disk F Disk Upload Disk The command completed successfully.
C:\>net use x: \\computer27\e System error 53 has occurred.
The network path was not found.
C:\>
-------------- Sleep is for the weak.
|
|
|
|
Post Number: 15
|
Wiley
©0®ÞØ®4+3 whØ®3
Group: Members
Posts: 1268
Joined: Oct. 2001
|
|
Posted on: Jun. 03 2002,06:07 |
|
|
You're killing me here ...I can't sleep when I know somewhere computers can't talk.
Double check (for my sanity) that "Enable NetBios of TCP/IP" is enabled on Computer27 and the problem computer (TCP/IP Properties/Advanced/Wins)
Check the version number on Netbt.sys to make sure it has not changed or is outdated. Latest version I have is 5.1.2600
This is not a 3Com Etherlink nic by chance is it?
Edit: Rule out security issues by using the admin account of the computer hosting the share.
net use x: \\computer27/e /user:computer27\administrator you should then be asked for a password. If this works then you have a security issue. I don't think this is the case however as you would have gotten a "you do not have permission to access the specified resource" error. But it does rule out a question of security.
-------------- There's a sucker born every minute ...but swallowers are hard to find.
|
|
|
|
Post Number: 16
|
Rshias
The Insomniac
Group: Members
Posts: 198
Joined: Jan. 2001
|
|
Posted on: Jun. 03 2002,06:20 |
|
|
All the NICs are: Realtek RTL8139's
The default option is selected for the WIN configuration on all the systems - verified. It enables NETBIOS over TCP/IP if none is provided by the DHCP server, or when static IPs are used.
Netbt.sys is also the latest version - verified. (comes standard with XP)
-------------- Sleep is for the weak.
|
|
|
|
Post Number: 17
|
Rshias
The Insomniac
Group: Members
Posts: 198
Joined: Jan. 2001
|
|
Posted on: Jun. 03 2002,06:33 |
|
|
Rule out security. The same result was returned - can't find path. The trouble system is also unable to map it's own drive, or access it's own data via the Run option: \\computer27\e
-------------- Sleep is for the weak.
|
|
|
|
Post Number: 18
|
Wiley
©0®ÞØ®4+3 whØ®3
Group: Members
Posts: 1268
Joined: Oct. 2001
|
|
Posted on: Jun. 03 2002,15:26 |
|
|
This is why god invented the OSI model. Quickie Layer check: 1. Physical- Cable plugged in 2. Data Link- Can both send and recieve data over the ethernet 3. Network- Has a valid IP and can ping remote hosts 4. Transport- Can form a valid packet and read returned data 5. Session- !!Cannot open communications with a remote host!! 6. Presentation- This is a stupid layer anyway 7. Application- Browsing applications function, but there is not network connection to remote resorces ...bummer
Based on the quickie layer check I'm still casting a vote for the browser service (NetBios) being fux0red. If you don't have duplicate names (use nbtstat -n to check for conflicts) and your not logging any errors to the event viewer then I would say reload TCP/IP and Client for Microsoft Networks only for lack of a better answer. There is always MS Support as I think we have ruled out most of the obvious I can thing of. You only have one NIC and one IP correct? You're not trying to team two NICs or anything like that? Is this a Workgroup or a Domain? If it is a Domain then (warning ...super obvious question coming) the computer has a machine account and is logging into the domain right?
-------------- There's a sucker born every minute ...but swallowers are hard to find.
|
|
|
|
|