Anyone know of a Network Neighborhood Replacement...

D

DariustheSandman

Weaksauce
Joined
Mar 15, 2005
Messages
107
I'm having trouble with network neighborhood, and I was wondering if I could just circumvent the problem entirely by using something else. If it could manage network shares that would be great as well. It also needs to work on Windows 7 64 bit. Thanks
 
Network Neighborhood is just a UI wrapper around net.exe? What are you trying to do?

This posting is provided "AS IS" with no warranties, and confers no rights.
 
You haven't needed Network Neighborhood in years to manage shares. You just set up the shares and then set permissions on them.
 
Well I can't seem to access the network shares on my main box ever since I switched to Windows 7 64 bit. All the rest of the computers on the network can see them, including a laptop with Windows 7 RC on it. I was just wondering if I could get around the problem somehow, since I wasn't having much luck fixing it directly.
 
Do you have file and print sharing blocked in the firewall? Can you ping the "server" by name and/or IP?
 
Definitely not the firewall...on or off, it's still a problem. I can ping the clients that have the shares...but network neighborhood and windows in general cannot see them.
 
and netbios of tcp/ip is enabled...just so ya know. That and I have no third party firewall or anti-virus programs that I'm aware of.
 
Can you access the computer by going Start > Run > \\Computer Name or \\IP? It should bring you directly to root of all the shared folder and devices for that PC. This will be a clear indicator whether or not you can connect to the computer.

If you can then;

Are your computers in the same Workgroup or Domain?
Is Home Group enable on the Windows 7 PC? What type of network did set you it to? Home, Work, or Public?
Do you have File and Sharing enabled on all computers and have you set the permission properly?
 
Jutsu said:
Can you access the computer by going Start > Run > \\Computer Name or \\IP? It should bring you directly to root of all the shared folder and devices for that PC. This will be a clear indicator whether or not you can connect to the computer.
Click to expand...

I can't access with the IP either. Same error as above.
 
Open network and sharing center. Click "choose homegroup and sharing options". Click "Change advanced sharing settings. What are the various bullets selected there?
 
Tawnos said:
Open network and sharing center. Click "choose homegroup and sharing options". Click "Change advanced sharing settings. What are the various bullets selected there?
Click to expand...

network discovery: on
file and printer sharing: on
public folder sharing: on
media streaming: on
40 or 56 bit encryption
password protected sharing off
Homegroup connections: off (using user accounts and passwords to connect)
 
You might not be running on the same network subnet.
Manually set IPs/Subnet/Gateway/DNS on all machines to see if it is working but you just arent getting IPs correctly.
 
Nenu said:
You might not be running on the same network subnet.
Manually set IPs/Subnet/Gateway/DNS on all machines to see if it is working but you just arent getting IPs correctly.
Click to expand...

The IPs are manually set. And if they were not on the same subnet, then the other machines would be having the same problem no? I have an XP machine and a Win 7 RC machine that can access the other machines just fine. In fact I just went back and double checked the Win XP machine and it still accesses all 3 machines just fine.
 
Check in device manager that the network cards are functional.
 
Device Mangler doesn't seem to have any issues with the network card. I've got an onboard NIC that's never managed to detect for some reason...guess that could be related somehow, but since Windows have never managed to even see the thing...I don't know. I'll try anything at this point.
 
Check the motherboard mfr website for an updated NIC driver.
Also check the NIC chip mfr website.
 
It's a realtek. I tried to get a driver, but Windows doesn't seem to be detecting the device at all. So unless the BIOS is reporting something to Windows that I can't see...it shouldn't be interfering should it?
 
Its possible that an unknown device on the same interrupt can interfere with operation, worth considering.
I meant that your network card that is struggling might benefit from a driver update.
 
If it is disabled in the BIOS, then it won't show up in Windows. I also had a motherboard once, an IC7 I think, that had the port for an onboard NIC, but none of the circuitry to ectually be a NIC. Realtek NICs are auto-detected in Windows 7, as far as my experience says.
 
Nenu said:
Its possible that an unknown device on the same interrupt can interfere with operation, worth considering.
I meant that your network card that is struggling might benefit from a driver update.
Click to expand...

ah well that card is a Linksys WMP300N...there hasn't been a driver update since 2007. I tried tracking down a new driver update that uses the same chipset a while back, but didn't have much luck there either. I might just say screw it and get another network card, but I don't really know if that's the issue.
 
is the machine a newly built one..as in add in the host\username to the acl on the shares?

didnt I read tehre is a new method to share data with ip6 p2p or something?
 
Assuming no one else has any ideas...could one of the admins drop this thread in the Networking forum and see if I have any luck there?
 
Also new issue: It seems it won't let me share anything on the main box now either. Every time I try to share something I get "Your folder cannot be shared".
 
Last edited:
You manually set IPs, why?

Try setting to DHCP and use a router to serve addresses.
 
If you can ping the machine but not access the shares, that's generally a permissions error.

From command line, what do you get if you do net use * \\server\share /user:username /p
?
 
Tawnos said:
If you can ping the machine but not access the shares, that's generally a permissions error.

From command line, what do you get if you do net use * \\server\share /user:username /p
?
Click to expand...

"This network location cannot be reached....try windows troubleshooter, etc.."
 
can you run ipconfig /all and post output here from the machine that CAN access the share and the one that CANNOT, as well as the share itself?
 
back to Jutsu's question - is the network set to Home, Public, Work? Workgroup or Domain?
 
Tawnos said:
can you run ipconfig /all and post output here from the machine that CAN access the share and the one that CANNOT, as well as the share itself?
Click to expand...

This is the WinXP Pro box (It can access all shares, both XP and W7)

Windows IP Configuration



Host Name . . . . . . . . . . . . : archangel

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : hsd1.tx.comcast.net.



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : hsd1.tx.comcast.net.

Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller

Physical Address. . . . . . . . . : 00-24-8C-26-72-38

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.2.4

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 67.15.31.131

4.2.2.6

67.19.0.10

Lease Obtained. . . . . . . . . . : Tuesday, January 19, 2010 1:40:16 PM

Lease Expires . . . . . . . . . . : Wednesday, January 20, 2010 1:40:16 PM


This is from the one that can't, Windows 7 Pro 64-bit on wireless:


Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : hsd1.tx.comcast.net.
Description . . . . . . . . . . . : Linksys Wireless-N PCI Adapter WMP300N
Physical Address. . . . . . . . . : 00-22-6B-A4-A2-AA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::cc3a:8676:e3c0:ac57%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, January 19, 2010 4:35:02 PM
Lease Expires . . . . . . . . . . : Wednesday, January 20, 2010 4:35:01 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 285221483
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-03-C3-93-B0-00-22-6B-A4-A2-AA
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.hsd1.tx.comcast.net.:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1.tx.comcast.net.
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:10eb:1aa9:9d36:5f77(Preferred)
Link-local IPv6 Address . . . . . : fe80::10eb:1aa9:9d36:5f77%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
 
Any reason why one machine is using router for DNS and the other is using ISP?? Or just for fun?? :p
 
You must log in or register to reply here.
Back
Top