Ah, that's helpful. What OS is on the other machines?
I suspect that it's using the guest account - the default in Home
edition of Windows - and the Pro system has advanced sharing (I think
that's what it was called) enabled.
I think this command is supported in Home. From a command line on one of
the other machines, use the command:
NET USE \\thinkpad\SHARE /user:thinkpad\USER *
Replace SHARE and USER with a valid share, and a valid user on the
machine. The command should prompt you for a password - make sure you
use valid credentials on the machine.
Then try to open the share again through Start | Run and see if it works.
If it does you'll need to either disable advanced sharing on the Pro
system, or, if the other machines are all Pro, enable advanced sharing
on the other systems. A home group may work, but I'm not sure as I spend
too much time in corporate environments to play with it.
Jamie
On 2012-12-14 12:07 AM, Winterlight wrote:
At 07:41 PM 12/13/2012, you wrote:
Do you just get the generic "Windows cannot access \\PROBLEM" when
you try to connect to it?
I get
----------------------------------------------------
\\Thinkpad is not accessible. You might not have permission to use
this network resource. Contact Admin of this server to find out if you
have access permissions.
Logon failure; account currently disabled.
----------------------------------------------------
but I never get asked for a user name and password so I don't know
what account it is referring to.
What happens if you ping the problem machine by IP address and name?
C:\>Ping 192.168.1.101
Pinging 192.168.1.101 with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time=2ms TTL=128
Reply from 192.168.1.101: bytes=32 time=2ms TTL=128
Reply from 192.168.1.101: bytes=32 time=2ms TTL=128
Reply from 192.168.1.101: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
Jamie
On 2012-12-13 8:21 PM, Winterlight wrote:
good idea but turning it off made no difference
At 11:39 AM 12/13/2012, you wrote:
Windows firewall settings. Disable windows firewall and see if that
resolves the issue. If so find the exclusion that fixes it.
On Thu, Dec 13, 2012 at 1:08 PM, Winterlight
<[email protected]>wrote:
> I have a Thinkpad that connects to my LAN wirelessly on the same
router
> that supports my Work group. It is not the only device that
connects to the
> LAN on wifi. My phone and two other laptops do as well. The other
devices
> are working fine on wifi.
>
> The problem laptop is running Win7 Pro and appears in the network
> listings of all other LAN members. The Thinkpad has shares
enabled. The
> laptop can connect and access the members of the LAN but none of
wired
> members of the LAN can connect to the laptop. My LAN is not set
up as a
> home group but as users with password. I am a bit leary of
homegroup. I
> have shares enabled on the laptop and all other settings look
correct. If I
> click on the name of the laptop in Network from another computer
it will
> search but can not find the laptop.
>
> I ran MS network troubleshooter diagnostics on the problem laptop
and it
> came back with = there are two devices performing NAT and only
one device
> should be doing this. But none of the other devices have any
problems so
> whatever the problem is it must reside on this computer. Any
ideas? Thanks.
>
> w
>
>
--
Jamie Furtner [email protected]
"I aim to misbehave"
- Malcom Reynolds (Serenity movie)
"It's not safe...
"For them."
- River Tam (Serenity movie)
--
Jamie Furtner [email protected]
"I aim to misbehave"
- Malcom Reynolds (Serenity movie)
"It's not safe...
"For them."
- River Tam (Serenity movie)
