Re: linskys BEFSR41 router problem
have you tried to rebooting the router?
Matt
"XYZ" <bloke@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:r1jif.93359$Es4.49669@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hello ppl, I have a linskys BEFSR41 and have set up a small network for 2
> computers. We are able to see each other and access the internet but are
> unable to share files.when i try to access the other pc I get this
> message:-
> mshome is not accessible. You might not have permission to use this
> network resource. Contact the admistrator of this server to find out if
> you
> have access permisions. The network path was not found. Can anyone tell
> me
> what I need to do? Using XP Pro on both machines and have allowed printer
> and file sharing.
>
> Peter
>
>
.
Relevant Pages
- Re: linskys BEFSR41 router problem
... I have a linskys BEFSR41 and have set up a small network for 2 ... > computers. ... > have access permisions. ...
(alt.os.windows-xp) - linskys BEFSR41 router problem
... I have a linskys BEFSR41 and have set up a small network for 2 ... computers. ... have access permisions. ...
(alt.os.windows-xp) - Re: The Hard Problem for Behaviorists
... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
(sci.cognitive) - Re: Networks : Workgroups and Domains. How Do I Use Them?
... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
(microsoft.public.windowsxp.network_web) - Re: {workgroup}"...is not accessible" after removing NWLINK
... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
(microsoft.public.windowsxp.network_web) |
|
