| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 141881 | 2016-03-15 10:36:00 | windows 10 network, mysteriously broken | Mirddes (10) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1417557 | 2016-03-16 22:03:00 | What do you get if you run net view from a command prompt on each comp? Also, 'nbtstat -n' will show which comp is the master browser. | linw (53) | ||
| 1417558 | 2016-03-16 23:16:00 | Isnt it too late to install insider on PC's that didnt previously have it ? thankfully not. for installation media go.microsoft.com for enrolling start menu/settings app/updates etc/advanced options/get insider preview builds |
Mirddes (10) | ||
| 1417559 | 2016-03-16 23:21:00 | master browser? 7033 |
Mirddes (10) | ||
| 1417560 | 2016-03-17 01:18:00 | Isnt it too late to install insider on PC's that didnt previously have it ? No BUT now you have to have a pre existing activated OS either W7 -W8.1 and the insider builds take over that. If you decide to leave the insider program, then the only builds that will activate in the future are the last public releases. What happens is if you get a public release the watermark bottom Right hand corner disappears, upgrade to a insider build and its back again. Prior to the first 10240 release, ( mid July I think it was - MS cut off the "FREE" install of W10 insider builds) you didn't have to have any OS at all installed, as long as you were in the insider account it will work. I've got two computers here, both originally had XP on them, wiped their drives installed the insider OS's and they have been going good as gold ever since. The third has had a W7 key originally. |
wainuitech (129) | ||
| 1417561 | 2016-03-17 01:47:00 | I was using the insider version when it first became available on a spare PC, then decided to buy windows and stopped using it. Does that mean I can still install it on a spare PC or will it have been tied to the hardware I was running it on? Bit of a Hijack I guess if you want to ignore it. |
dugimodo (138) | ||
| 1417562 | 2016-03-17 01:59:00 | ignore the fictions i shall :) we are obligated to ignore unjust legalities such as legal fictions' (corporations) right's taking presidence over human rights. with all the copies of windows i've been through over the years, they have gotten rather cheeky, far too big for their imagined boots. |
Mirddes (10) | ||
| 1417563 | 2016-03-17 03:57:00 | I was using the insider version when it first became available on a spare PC, then decided to buy windows and stopped using it. Does that mean I can still install it on a spare PC or will it have been tied to the hardware I was running it on? Bit of a Hijack I guess if you want to ignore it. Narrrrr nothing like good hijack. If you put a newer insider build back on a previous PC AFTER 10240 ( hardware already activated ) it should reactivate, if its a different motherboard, then nope- W7-8.1 license required now. The old keys prior to 10240 have been blocked. From what I read if you haven't upgraded since pre 10240 and its the same hardware then you have to put in a pre 10240 insider build, THEN upgrade to the latest. Back on subject: Mirddes -- Still didn't answer the question Post #8 ? The reason for asking is had the similar and same thing happen on four different locations over the last week. And the answer is not what you may think ;) |
wainuitech (129) | ||
| 1417564 | 2016-03-17 05:05:00 | the other computers can access network shares on all other computers with the exception of server. \\server\ lists outdated shares and none of the shares are accessible. accessing 'server' using \\192.168.20.3 works flawlessly from all locations on the network. there is nothing special about server other than it being the computer the big hard-drive is in. what could the answer be? |
Mirddes (10) | ||
| 1417565 | 2016-03-17 05:22:00 | (Artificial) connection limit for being not a $erver OS? It used to be 10 on XP pro edit: not that if the IP works Netbios name resolution borkage (duplicate names anywhere?) |
fred_fish (15241) | ||
| 1417566 | 2016-03-17 06:22:00 | If the Others can all see and work correctly then its not the same problem I've solved. SO some questions, not really made clear in the posts. Some basic trouble shooting questions and something to try. ( adding to Freds Post) All of this can be tried within a few seconds, but of course no one can see what you can :) 1.What Build is the "Server" ? ( type winver into the search and open) 2.Can you actually see the folders ? If so, next question-> If no then ignore next question. 3.When trying to access, are there any sort of error messages ? 4. Was there any sort of updates installed then it lost access ? 5. Can you access the folders Via a Mapped network drive setup ? If you're not to sure how, open This PC, in a blank space in Network Locations right click - Add a Network Location -- Follow instructions. There was a patch that came out the other day, did some serious damage to some winsocks. To fix that open a CMD as Admin, •Type netsh winsock reset and press Enter. •Type netsh int ip reset and press Enter. •Type ipconfig /release and press Enter. •Type ipconfig /renew and press Enter. •Type ipconfig /flushdns and press Enter Reboot the computer and take off (if it hasn't already - should have) the static IP address, let the router give it another, if you can access the shares then reset the Static IP to whatever it now has. |
wainuitech (129) | ||
| 1 2 | |||||