Sign in with
Sign up | Sign in
Your question

Network Share Issue

Last response: in Networking
Share
July 14, 2012 3:36:46 PM

I am having an issues accessing my shares on my network.
My network is just a Vista desktop and a Win7 laptop connected to a Linksys router (laptop is wireless) and to a modem.

I cannot access my shares between computers. It just hangs and says it cannot find the path. Both computers HAVE internet connectivity. I have reset the shares, checked permissions, ensured they are in the same workgroup, reset the router, tried a new router...nothing.

This same exact thing happened to me several months ago and I either fixed it by dumb luck or something worked itself out. Pretty sure that last time it happened after a windows update...and there was just an update this time. I have changed nothing else.

Any help or suggestions would be appreciated.

More about : network share issue

July 15, 2012 4:18:28 PM

I have mine set up with the same user name etc. on both computers and it does not work. Thank you for suggestion though.

NEW INFO: If I go to command line and RELEASE the ip...tada, everything works. Except I obviously do not have an internet connection. So i then RENEW....then I'm back to my same issue of not being able to access shares.

Anyone know why this might be? My addresses are set up dynamically and I checked the addresses on both machines and they are not conflicting.
m
0
l
Related resources
July 15, 2012 5:16:57 PM

If releasing the DHCP lease now makes it work, that's very strange. Because at that point you don't have a local IP at all. An ipconfig should now return 0.0.0.0/0.0.0.0, not just a missing gateway IP (which is specifically needed for Internet access). Not unless the system is retreating to raw SMB once TCP/IP is unavailable.

I suggest uploading an "ipconfig /all" for both cases, let's compare them and see what's different. Because some things are not making sense here.
m
0
l
July 15, 2012 5:54:54 PM

This is before I do anything and I’m having an issue accessing my other computer

Windows IP Configuration
Host Name . . . . . . . . . . . . : LauppLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : wildblue.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : 00-26-82-F1-F6-DD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2df6:e794:e591:2897%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.5.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, July 15, 2012 12:38:48 PM
Lease Expires . . . . . . . . . . : Monday, July 16, 2012 12:38:48 PM
Default Gateway . . . . . . . . . : 192.168.5.1
DHCP Server . . . . . . . . . . . : 192.168.5.1
DHCPv6 IAID . . . . . . . . . . . : 318776962
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-4E-3F-F2-88-AE-1D-DD-1F-92

DNS Servers . . . . . . . . . . . : 208.67.220.220
208.67.222.222
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 88-AE-1D-DD-1F-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.wildblue.com:

Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.5.101%16(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 208.67.220.220
208.67.222.222
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 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:9e76:20ed:1472:bcc9:282b(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::20ed:1472:bcc9:282b%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled



This is after I do “ipconfig /release”

Windows IP Configuration

Host Name . . . . . . . . . . . . : LauppLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : 00-26-82-F1-F6-DD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2df6:e794:e591:2897%13(Preferre
Autoconfiguration IPv4 Address. . : 169.254.40.151(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 318776962
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-4E-3F-F2-88-AE-1D-DD-1

DNS Servers . . . . . . . . . . . : 208.67.220.220
208.67.222.222
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 88-AE-1D-DD-1F-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.wildblue.com:

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

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{293F5810-C4CF-429C-B2E5-5288699FEBF1}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
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


Then if I renew it, it will go back to the prior config and not work.
m
0
l
July 15, 2012 10:05:01 PM

Ok, here’s what we know so far. Looking at the normal situation, I can see your computer is being assigned an IP of 192.168.5.101 and a gateway IP of 192.168.5.1. When you release the DHCP lease, Windows is self-assigning an IP in the 169.254.x.x range. That threw me for a moment because under XP, Windows just left the IP as 0.0.0.0. But apparently MS decided to have Windows 7 use APIPA addressing under such circumstances. Just caught me off-guard, but that’s fine, that’ll work. But as you’ve seen, there’s no gateway IP under APIPA.

The fact BOTH computers will function normally using APIPA addressing, but NOT when using the router, suggests that each computer is being configured differently when using DHCP, almost as if one is behind the primary router, and the other is perhaps behind a different router, or using ICS, or … something. But once they’re forced to resort to APIPA addressing (which means no DHCP server is available), now they’re on the SAME network and can communicate normally (but w/o internet access, of course).

What I’m wondering is if perhaps you’re trying to use a second router behind one of your computers, maybe to use its switch, AP, etc., and forgot to disable its DHCP server! If that was the case, then it’s possible both computers would be using different DHCP servers, thus different networks, and can’t communicate.

Perhaps we need to compare the ipconfig of both machines when running normally to confirm they’re on the same network. Because I can’t see how they could use APIPA addressing and work, yet use the same router and DHPC server (and by extension, the same network) and not work. Just doesn’t make sense. Something else is in the picture here (like that second router I mentioned above) that’s not being identified to explain this odd behavior.



m
0
l
July 15, 2012 11:21:36 PM

The only other hardware on the network is the modem...there is no other router.

Do you want the ipconfigs for both machines when I release and can access shares....or the default configuration when they have internet but can't share?
m
0
l
July 15, 2012 11:27:40 PM

Just the default configurations for now.
m
0
l
July 15, 2012 11:30:44 PM

P.S. It wouldn't hurt to do a factory reset on the router. Start fresh. These are imperfect devices, and they just get screwed up and produce weird behavior from time to time. At the very least we'll know there's nothing you did in the way of reconfiguration to affect this problem.
m
0
l
July 16, 2012 12:20:38 AM

As I stated in my OP, I did a factory reset but it did nothing. I did it again just for good measure...nothing. Like I said in my OP as well, I also tried a different router and it did the same thing.

Below are the configurations for my laptop and desktop that are automatically assigned.
The only thing I noticed that was different were the "node types". One is "hybrid" and one is "peer-to-peer"...IDK anything about that though.

Windows 7 Laptop

Windows IP Configuration

Host Name . . . . . . . . . . . . : LauppLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : wildblue.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : 00-26-82-F1-F6-DD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2df6:e794:e591:2897%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, July 15, 2012 7:02:40 PM
Lease Expires . . . . . . . . . . : Monday, July 16, 2012 7:02:40 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 318776962
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-4E-3F-F2-88-AE-1D-DD-1F-92

DNS Servers . . . . . . . . . . . : 208.67.220.220
208.67.222.222
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 88-AE-1D-DD-1F-92
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.wildblue.com:

Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.101%16(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 208.67.220.220
208.67.222.222
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 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:9e76:862:30bb:bcc9:282b(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::862:30bb:bcc9:282b%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Windows vista desktop

Windows IP Configuration

Host Name . . . . . . . . . . . . : LauppDesktop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : wildblue.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1E-8C-A0-1C-F9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c0c5:3362:cb99:6217%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, July 15, 2012 6:54:00 PM
Lease Expires . . . . . . . . . . : Monday, July 16, 2012 7:06:15 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 167779980
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-94-74-F2-00-1E-8C-A0-1C-F9

DNS Servers . . . . . . . . . . . : 192.168.1.1
12.213.80.61
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : wildblue.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:70:21fe:3f57:fe9b(Prefer
red)
Link-local IPv6 Address . . . . . : fe80::70:21fe:3f57:fe9b%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled


m
0
l
July 16, 2012 1:02:35 AM

Well everything seems fine wrt the IP address, subnet mask, and gateway IP of both the laptop and desktop. They're both using the same network (192.168.1.x) and gateway, 192.168.1.1 (the router's IP address). But I did notice a couple oddities.

First, the network changed (it was 192.168.5.x before). With a reset that's to be expected, but it did indicate that you had made changes to the router’s default network, perhaps more.

More importantly, why are the DNS servers different? In the case of the laptop, it's 208.67.220.220, 208.67.222.222, but for the desktop it's 192.168.1.1, 12.213.80.61. Putting aside for the moment whether this could spell trouble just by itself, it suggests the TCP/IP configurations on each computer are different, that perhaps one of them is overriding the DNS servers manually, and who knows what else. There's no way that these two computers should show differences like this unless their respective TCP/IP configurations have been changed/modified. PLACE THEM BACK TO ALL DEFAULTS ON EVERY OPTION.

Again, maybe the differences in DNS servers doesn’t matter (maybe it does), but it suggests that these two computers ARE DIFFERENT, perhaps in other ways as well.
m
0
l
July 16, 2012 1:06:37 AM

PROBLEM FIXED:

As stated, the node types were different for the two machines. After poking around with google I read that the "peer-to-peer" node type had caused some issues when used in conjunction with other node types.

I went into the registry and changed the node type on the vista machine from "peer-to-peer" to "hybrid". I rebooted both machines and everything is working fine now...or at least for the moment.

Thank you eibgrad for your help in this matter.
m
0
l
July 16, 2012 1:09:48 AM

My bad about the DNS.

I use opendDNS and had it configured to that. In attempt to fix the issue I set it to obtain one automatically...I must have done it between getting the ipconfig information.

They both have the same DNS I just accidentally changed it between.

Thanks again.
m
0
l
!