Win 7 Pro can't find T3 shares

[xlrcomm]

Hi All,

Have read through the forum, tried various things and my Win7 Pro machines can not access the T3 shares.
My XP and Win7 Home machines have no problem accessing, so it is a Pro issue. Win 7 will show BEYONWIZT3 under Networks but then errors when I click on. "Windows cannot access \\BEYONWIZT3".

Checked Windows sharing options and password protected sharing is off.

Any ideas please?

Thanks,
Rick

[simoncasey]

Can you access it if you enter the t3's IP address directly?

[simoncasey]

Most of the issues people have had is with the T3 accessing the windows shares rather than the issue you are having. So password protected sharing etc won't affect your issue.

Also worth checking the obvious that you can access other devices from your win7 pro pc.

[xlrcomm]

Most of the issues people have had is with the T3 accessing the windows shares rather than the issue you are having. So password protected sharing etc won't affect your issue.

Also worth checking the obvious that you can access other devices from your win7 pro pc.

Hi Simon,
All other devices are ok and have been for a long time. The T3 is a new addition and It's the only device that is having issues, on any Win7 Pro machine.
Using \\IP works fine. Both Hardisk and Root shares are accessible. \\BEYONWIZT3 gives access error. I can use PuTTY and SCP to login directly.

I also have 2 linux based NAS on my network that give no access issues with Win7 Pro.

All other network devices are accessible using \\DEVICENAME so I want to access the T3 the same way. Makes it easy to get to using any file manager software.

[gra]

just a thought. try disabling your anti-virus software.

[simoncasey]

Most of the issues people have had is with the T3 accessing the windows shares rather than the issue you are having. So password protected sharing etc won't affect your issue.

Also worth checking the obvious that you can access other devices from your win7 pro pc.

Hi Simon,
All other devices are ok and have been for a long time. The T3 is a new addition and It's the only device that is having issues, on any Win7 Pro machine.
Using \\IP works fine. Both Hardisk and Root shares are accessible. \\BEYONWIZT3 gives access error. I can use PuTTY and SCP to login directly.

I also have 2 linux based NAS on my network that give no access issues with Win7 Pro.

All other network devices are accessible using \\DEVICENAME so I want to access the T3 the same way. Makes it easy to get to using any file manager software.

I had the same problem with my win7 pro machine too. Ie I can access it ok but name resolution didn't work. You need something to provide name resolution internally on your Network. That can be through your router or you will need to enable netbios over tcp/ip or I think bonjour will do it as well if you are an apple person and have iPads networked. I think netbios was installed by default on windows xp. Otherwise you can go old school and add an entry in the hosts file on the PC but that would only work if the IP address on the t3 was fixed.

[xlrcomm]

I had the same problem with my win7 pro machine too. Ie I can access it ok but name resolution didn't work. You need something to provide name resolution internally on your Network. That can be through your router or you will need to enable netbios over tcp/ip or I think bonjour will do it as well if you are an apple person and have iPads networked. I think netbios was installed by default on windows xp. Otherwise you can go old school and add an entry in the hosts file on the PC but that would only work if the IP address on the t3 was fixed.

Seems to be fixed Think due to the router for some reason having 2 entries for the T3.
Cleared those entries, low and behold Win7 Pro now working as it should, on both machines. Why the router was screwed, dunno ........ FRITZ!Boxes are usually pretty good. Strange.

Thanks for the help

[xlrcomm]

Aaarrgghh! I give up
Tried this morning and now it's not working.

Back to the drawing board

[prl]

Do you have two entries for the T3 in your fritzbox again?

[xlrcomm]

Do you have two entries for the T3 in your fritzbox again?

Only the one. It's setup for static IP. Rebooted the T3 and access is available again.

Think the 2 entries was a clash from the old DP-P2 (replaced by T3 and no longer in service) which used the same IP, only the name and MAC was different.

[simoncasey]

Do you have two entries for the T3 in your fritzbox again?

Only the one. It's setup for static IP. Rebooted the T3 and access is available again.

Think the 2 entries was a clash from the old DP-P2 (replaced by T3 and no longer in service) which used the same IP, only the name and MAC was different.

When you say static IP so you mean static IP configured on the T3 or have you for a permanent IP address assign to the MAC from the router.

[xlrcomm]

When you say static IP so you mean static IP configured on the T3 or have you for a permanent IP address assign to the MAC from the router.

Both. Set in the T3 and via MAC in the router.

[simoncasey]

When you say static IP so you mean static IP configured on the T3 or have you for a permanent IP address assign to the MAC from the router.

Both. Set in the T3 and via MAC in the router.

If you are going to set a fixed IP for the T3 in your router then the T3 should be configured for DHCP and not a static IP.

[peteru]

When you say static IP so you mean static IP configured on the T3 or have you for a permanent IP address assign to the MAC from the router.

Both. Set in the T3 and via MAC in the router.

That's your problem. The router never sees the T3. Set your T3 to DHCP and you'll be fine.

[prl]

When you say static IP so you mean static IP configured on the T3 or have you for a permanent IP address assign to the MAC from the router.

Both. Set in the T3 and via MAC in the router.

If you are going to set a fixed IP for the T3 in your router then the T3 should be configured for DHCP and not a static IP.

The story on the FRITZ!Box 7390 (which I have, not sure what the OP's FRITZ!Box is) is a bit more complicated.

It appears to be possible to type in fixed MAC -> IP assignments for DHCP in the 7390. They are created in the 7390 Web interface in Home Network>Network>Devices and Users, Add device. If you add IP addresses there, the IP address should be in the range reserved for DHCP (see below), and should be different from any IP address already assigned to a device in the Devices and Users page.

Alternatively, you can lock down an existing DHCP MAC -> IP address assignment in the Devices and Users by clicking on the device's edit (pencil) icon, ticking "Always assign this network device the same IPv4 address", and then clicking OK. IMO this is the simplest and safest way of creating a fixed DHCP MAC -> IP address mapping. I've actually used that.

If you want to use the DHCP mechanism (with fixed or dynamically assigned MAC -> IP address mappings), set the T3's network setup to use DHCP. Don't use a manually assigned IP address on the T3 in this case.

If you want to assign a fixed IP for the T3 in the T3, then its IP address should not be in the range of IP addresses for reserved DHCP allocation. I haven't tried this, and I wouldn't recommend it, unless you absolutely have to. It's much cleaner to manage all IP addresses through the router's DCHP facilities.

On the 7390 the default IP range reserved for DHCP is 192.168.178.20 - 192.168.178.200. Fixed IP addresses on the network should unique and in the ranges 192.168.178.2 - 192.168.178.19 or 192.168.178.201 - 192.168.178.254. The router is 192.168.178.1 by default, and 192.168.178.0 and 192.168.178.255 are reserved.

It's possible to change the DHCP allocation range on the 7390 to something else, but it's probably best left as it is.

[xlrcomm]

Spot on Peter, in all your points.

I use the FRITZ!Box 7490.
In my network, fixed IP devices have a specific range and DHCP devices use another. Allocations have been changed from the default so as to fit the network. The 7490 replaced a Billion router.

[prl]

But more importantly, have you been able to sort out the IP address issues so that your shares wok properly?

[xlrcomm]

But more importantly, have you been able to sort out the IP address issues so that your shares wok properly?

Well, seems to be working ok. Checked this morning and no hassles

[prl]

[simoncasey]

Spot on Peter, in all your points.

I use the FRITZ!Box 7490.
In my network, fixed IP devices have a specific range and DHCP devices use another. Allocations have been changed from the default so as to fit the network. The 7490 replaced a Billion router.

Just to confirm, you have your T3 configured to use DHCP and it gets allocated a fixed IP from the router. The T3 isn't configured for static IP.

[xlrcomm]

Just to confirm, you have your T3 configured to use DHCP and it gets allocated a fixed IP from the router. The T3 isn't configured for static IP.

T3 is configured for static and fixed IP allocated in the router. All working fine now.
Every other device on the network is configured the same way. Never had a problem until the T3.

[simoncasey]

Just to confirm, you have your T3 configured to use DHCP and it gets allocated a fixed IP from the router. The T3 isn't configured for static IP.

T3 is configured for static and fixed IP allocated in the router. All working fine now.
Every other device on the network is configured the same way. Never had a problem until the T3.

That's not how you should have your network configured. If you are allocating fixed IPs from your router, then your devices should be configured for DHCP, you shouldn't be configuring both a static IP on the device and allocating a specific IP to the device from the router.

[peteru]

It's actually not the T3 that was having the problems. It was the other devices that could not find the T3. It seems like your network is still not configured properly, as Simon points out.