Link to home
Start Free TrialLog in
Avatar of BeGentleWithMe-INeedHelp
BeGentleWithMe-INeedHelpFlag for United States of America

asked on

File sharing between 2 windows 10 machines using username / password - not working. Thoughts

I set up file sharing between 2 computers on a LAN

Machine A can see a folder on machine B
Machine B can see a folder on machine A.

At least that's how it was working.

Now, machine A can't see the folder on machine b. I had a shortcut \\machineB\docs.  Clicking on it now, gets windows cannot access \\machineb\docs.

on machine A, I can ping machine B by IP and by machine name.

On machine B, if I type \\machineb in win explorer, I see the folder being shared and can browse it.
On machine A, if I type \\machineb in win explorer, I get the 'cannot access...' message .  clikcing on details says 'the network path was not found.

I turned off the firewall on both machines.  still no change.

I created another share on machine B.  I can see it on machine B, but can't see that one either on machine A.

In networking, sharing:
Both on / checked;  network discovery and turn on auto setup of network connected devices
File printing - turn on file and printer sharing is checked
homegroup: use user accounts and passwords to connect to other computers is checked.

Both machines are in the same workgroup.
Both are in the private network profile
 
any thoughts on how to troubleshoot this / what am I missing?
SOLUTION
Avatar of Wayne88
Wayne88
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of BeGentleWithMe-INeedHelp

ASKER

Thanks guys.  I'm not sure how I missed this. machine a pings machine b at the wrong IP address. (192.168.1.6 rather than .7 which is machine B's current IP address

i did ipconfig /flushdns on machine A
there's no entries in the hosts file on machine A

I guess machine A getting the ip address of machine B from the fios router (which is dns and dhcp server also) and I don't have the login for that (working remote and thought I had a picture of the label with login info)?

I say that and that doesn't make sense,right? If router gives machine B a new ip address, it 'should' update the DNS listings, right?  the problem is on machine a and a cached ip address for machine B?

I rebooted machine A & B.  problem persists...
DNS uses host file, cashes, router, and more.  Best to assign static IPs and access with \\192.168.123.123\Share
You're welcome
OK, starting kinda from scratch.  Machine A - I'll call A, machine B, i'll call B.  B has some files that we were able to get to from A when typing \\a\docs.  B is a laptop.....that has 2 NICs - 1 wired, 1 wireless.

now it's not working.

If I type ping b on A, it comes back with 192.168.1.6 and no response.

On B, the active IP address is 192.168.1.7 (via the wired connection)

Looking at Verizon FIOS router that does DHCP,

the leases show,besides others:

B                 192.168.1.6 (with the wireless MAC address)
newhost4 192.168.1.7 (with the wired MAC address)

the lease time is 1440 so the 192.168.1.6 will fall out at some point.

But brings up a question... with machine name A, you connect to your lan with ethernet AND wireless...  2 IP addresses.  What machine name should both IPs be related to in the DHCP table?

In the fios router box, there's a check box to 'provide host name if not specified by client.  That was checked, and likely how it came up with newhost4 name?  

I unchecked it.  but

a) why would the machine not give its machine name in the DHCP process on the wired connection, but DID give the machine name on wireless?

b) I found this

http://mscottford.com/post/25106788989/updated-fixed-verizon-router-keeps-changing-my

That was from years ago and says the problem is solved for only a short while.

thoughts?

if they connect the laptop to LAN sometimes wirelessly and sometimes wired, shoudln't the other machines be able to get to the files either way?

Should I shorten the lease so when they take the laptop out of office, the wireless connection lease falls out sooner and hopefully won't be there when laptop connects again over a wire?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial