From: invalid@invalid.invalid   
      
   "Java Jive"  schrieb im Newsbeitrag   
   news:va0k2bpvkbeptg9pi8jcc2ds0098nqagpn@4ax.com...   
   > Well, there's not much to go on in your OP, which is why originally I   
   > didn't reply to it.   
   >   
   > It is important to know whether:   
   >   
   > ? You can use your browser on the internet   
      
   yes I can   
      
   > Presumably so, because you are posting here, but if not because you   
   > used another PC for this, troubleshoot network connectivity  - network   
   > card appears normal in Device Manager, network cable pushed in to back   
   > of PC properly, netword card lights coming on and flashing with data   
   > transfer, router is up and running, etc.  What happens when on the   
   > affected PC you type ipconfig /all into a command prompt.  Do you get   
   > an address in the subnet ...   
   > 169.254.0.0/255.255.0.0 Self-assigned address, no connection   
   > ... or more hopefully in one of the three private subnets used for   
   > DHCP IP address assignment ...   
   > 10.0.0.0/255.0.0.0 Probably DHCP assigned = connection   
   > 172.16.0.0/255.240.0.0 Ditto (but very rarely used)   
   > 192.168.0.0/255.255.0.0 Ditto (most commonly used range)   
   > Note:  If, rather unusually, you have fixed IPs, then all bets are   
   > off, you will have to check manually that all the IPs on the network   
   > fall into the common range desired.   
      
   I can do all in the network except than export shares   
      
   > ? You can see other computers in network neighbourhood   
      
   yes I can   
      
   > In Computer Management, the Browser service must be running, and one   
   > on the machines on the network, usually the first to power up, must   
   > have been elected a BrowserMaster.  I won't go into this here, because   
   > it rarely goes wrong unless someone has been fiddling deeply, and   
   > furthermore it's quite complicated to remember, so I'd have to look it   
   > all up.  Also, AFAICR, even if this was not working, you'd still be   
   > able to ping other machines and connect to them by typing   
   > \\Server\Share into Explorer's address bar.   
      
   The browser service is running.   
      
   > ? All shares are affected, or just this one you are trying to   
   > create in the OP.  From your OP, I got the impression all, but you   
   > didn't specifically say that.   
      
   All shares of that one computer   
      
   > If all, then start with the firewall settings:   
   > Control Panel   
   > Windows Firewall   
   > Exceptions   
   > File and Printer Sharing Checked   
   > Edit   
   > TCP139 Checked   
   > TCP445 Checked   
   > UDP137 Checked   
   > UDP138 Checked   
   > ... for each, check ...   
   > Change Scope   
   > ... usually ...   
   > My network (subnet) only   
   > ... but can be ...   
   > Custom list*   
   > ... for example ...   
   > 169.254.0.0/255.255.0.0   
   > 192.168.0.0/255.255.0.0   
      
   I just checked the settings. Nothing suspicious.   
      
   > * Here these entries have been written on seperate lines to avoid   
   > corruption by linewrap, but in reality are on one line seperated by   
   > commas ...   
   > 169.254.0.0/255.255.0.0,192.168.0.0/255.255.0.0   
   > In the settings suggested, the first line allows a fallback direct   
   > connection between two devices via a crossover cable**, which can be   
   > useful when a router fails, or you have no router because you are   
   > trying to back up to another device in a hotel, etc.  The second is   
   > the more normal and important setting, and usually lies in one of the   
   > three private subnet ranges given when discussing basic connectivity   
   > above.   
   >   
   > ** Nowadays many network cards do not need a crossover cable, but can   
   > automatically sense and adjust appropriately to whichever type of   
   > cable is used, normal straight through or crossover.   
   >   
   > If just this specific share is failing, then this is most probably a   
   > permissions problem.  It's not just the Share Permissions that matter,   
   > but also the ownership and permissions on the directory that is   
   > shared.   
   >   
   > The default permissions on Windows shares are appallingly lax, even   
   > still in Win10.  The permissions for a general share should be ...   
   > Administrators Fuil control   
   > System Full control   
   > Authenticated Users Either Read or Modify as desired   
   > ... but for your own documents as here I would use ...   
   > Administrators Fuil control   
   > System Full control   
   >  Modify (presumably, could be Read)   
   >   
   > Similarly, the normal settings on a Personal Folder would be something   
   > like ...   
   > Administrators Fuil control (by default may be absent)   
   > System Full control   
   >  Full control   
   > CREATOR OWNER Special   
   > ... and they should be replicated throughout subfolders via ...   
   > Security   
   > Advanced   
   > Replace permission entries on all child objects ..., OK   
   >   
   > The owner of the folder and subfolders should likewise be set either   
   > to Administrators or the user, possibly System.  I can't remember what   
   > the default usually is, but I use Administrators.   
   >   
   > On Mon, 19 Oct 2015 15:17:49 +0200, "Heinrich Wolf"   
   >  wrote:   
   >   
   >> Hi,   
   >>   
   >> any other recomendations?   
   >>   
   >> Heiner   
   >>   
   > --   
   > ========================================================   
   > Please always reply to ng as the email in this post's   
   > header does not exist.  Or use a contact address at:   
   > http://www.macfh.co.uk/JavaJive/JavaJive.html   
   > http://www.macfh.co.uk/Macfarlane/Macfarlane.html   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)