TCP/IP Sharing Problem

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

I have two computers running WinXP Pro that are networked. They can
both access the internet and both can see the other computer. I also
have sharing rights on some folders, but others are not allowed.

I am wanting full access to the C drive on both computers.

I get the following message when I try to access the "Windows"
folder; the "Program Files" folder; or the "Documents and Settings"
folder on the other computer.

"other\computer\folder is not accessible. You might not have
permission to use this network resource. Contact the administrator of
this server to find out if you have access permissions. Access is
denied."

I am able to fully access the same folders of the computer I am
working on (through the network) but not the other computer's folders.

This seems like it would be a simple security setting. Am I asking for
help in the right group? What setting needs to be adjusted? I have
scoured the internet and 'google groups' for a solution to no avail.

OTHER INFO:

Network Hardware: Netgear Gateway Router Model RT314
Linksys USB Printserver PPS1UW

The only way I could get the printserver to work on either computer
was to designate an IP address at the TCP/IP Alternate Configuration.
I was having the same problems with sharing before this was
configured.

I also use ZoneAlarm Pro and it was disabled during all testing on
both computers. Simple File Sharing is now checked on both computers
although I did have it unchecked at times trying to get this to work.
I have also set a password for each computer at logon. I have used
TweakUI to automatically logon in the past, but have also disabled
this feature while testing. Under EVERYONE I have granted full
control for each folder in question.

What can I do to gain full access to all folders on the C drives?

Thanks, Scott
 
I have two computers running WinXP Pro that are networked. They can
both access the internet and both can see the other computer. I also
have sharing rights on some folders, but others are not allowed.

I am wanting full access to the C drive on both computers.

I get the following message when I try to access the "Windows"
folder; the "Program Files" folder; or the "Documents and Settings"
folder on the other computer.
[/QUOTE]

If you RTFM (i.e. the winsux help file) you will see that these folders
are not shareable. (To be honest, I don't read it either; it took me
months to discover this)
"other\computer\folder is not accessible. You might not have
permission to use this network resource. Contact the administrator of
this server to find out if you have access permissions. Access is
denied."

I am able to fully access the same folders of the computer I am
working on (through the network) but not the other computer's folders.

This seems like it would be a simple security setting. Am I asking for
help in the right group? What setting needs to be adjusted? I have
scoured the internet and 'google groups' for a solution to no avail.

OTHER INFO:

Network Hardware: Netgear Gateway Router Model RT314
Linksys USB Printserver PPS1UW

The only way I could get the printserver to work on either computer
was to designate an IP address at the TCP/IP Alternate Configuration.
I was having the same problems with sharing before this was
configured.

I also use ZoneAlarm Pro and it was disabled during all testing on
both computers. Simple File Sharing is now checked on both computers
although I did have it unchecked at times trying to get this to work.
I have also set a password for each computer at logon. I have used
TweakUI to automatically logon in the past, but have also disabled
this feature while testing. Under EVERYONE I have granted full
control for each folder in question.

What can I do to gain full access to all folders on the C drives?

Buy Linux.
 
Why do you imagine this has anything to do with TCP/IP?

Nobody said it did. If you RTFPost you'll see that I'm unsure where
to ask such a question. It just so happens that this is the only
protocol that I use.
If you RTFM (i.e. the winsux help file) you will see that these folders
are not shareable. (To be honest, I don't read it either; it took me
months to discover this)

Never had this problem with WIN98.
Buy Linux.

I wish I had the time to invest in learning this OS.
 
Nobody said it did. If you RTFPost you'll see that I'm unsure where
to ask such a question. It just so happens that this is the only
protocol that I use.

That is another reason for your shares failing. TCP/IP does not share
files on a LAN. You must use NETBEUI. (you must be using it or you
would not have got the error message)

Never had this problem with WIN98.

This was a facetious remark.
I wish I had the time to invest in learning this OS.

Yes, we spend all our time becoming expert with today's product, and we
don't see tomorrow's product catching up until we find ourselves on the
scrapheap with knowledge that nobody wants.
 
That is another reason for your shares failing. TCP/IP does not share
files on a LAN. You must use NETBEUI. (you must be using it or you
would not have got the error message)


Netbeui is a networking protocol which can be used on a LAN in place
of (or alongside) tcp/ip, but it is NOT required. It is quite okay to
use tcp/ip as the only protocol.

Maybe you mean netbios and not netbeui? Netbios (the session layer
api) is used over tcp/ip in connection with file and printer sharing
(naming) but the file handling is achieved via the smb protocol.

http://samba.anu.edu.au/cifs/docs/what-is-smb.html



Jim
 
Netbeui is a networking protocol which can be used on a LAN in place
of (or alongside) tcp/ip, but it is NOT required. It is quite okay to
use tcp/ip as the only protocol.

If you use NETBUEI in place of TCP/IP you will lose internet access. IP
is Internet Protocol.
Maybe you mean netbios and not netbeui? Netbios (the session layer
api) is used over tcp/ip in connection with file and printer sharing
(naming) but the file handling is achieved via the smb protocol.

NETBUEI is NETBIOS Extended User Interface.
As an end user I see no difference between them. I am offered one or
the other and they both work.

I was using NETBIOS to share files between DOS boxes before the
Internet, and TCP/IP, was invented. NETBIOS is independent of TCP/IP
and is sufficient for file sharing.

I was restricting my advice to bog standard Windows options. You can
also use NFS to share files over TCP/IP but that does not help your
average Windows user.
 
If you use NETBUEI in place of TCP/IP you will lose internet access. IP
is Internet Protocol.

Re-wind a little, John. You told the guy "You must use NETBEUI" which
is 100% wrong.

I said "netbeui...can be used on a LAN in place of (or alongside)
tcp/ip". This is correct. I didn't say netbeui could be used over the
Internet.
NETBUEI is NETBIOS Extended User Interface.
As an end user I see no difference between them. I am offered one or
the other and they both work.

Best you remain an end user then.
I was using NETBIOS to share files between DOS boxes before the
Internet, and TCP/IP, was invented. NETBIOS is independent of TCP/IP
and is sufficient for file sharing.


I was restricting my advice to bog standard Windows options. You can
also use NFS to share files over TCP/IP but that does not help your
average Windows user.

If you knew what you were talking about or bothered reading up a
little, you would know that "bog standard Windows" is already a smb
client and server without any third party functionality like NFS. It's
what you use when you drag and drop from windows explorer.


Jim.
 
I was using NETBIOS to share files between DOS boxes before the
Internet, and TCP/IP, was invented.

<snip>

That's pretty unlikely, since NETBIOS is a PC protocol, and the Internet
(or at least its predecessor, the ArpaNet), was around long before the
first PC.
 
(e-mail address removed) wrote:


<snip>

That's pretty unlikely, since NETBIOS is a PC protocol, and the Internet
(or at least its predecessor, the ArpaNet), was around long before the
first PC.

Well that claim was a bit sloppy, but my notes suggest that the IBM PC
appeared in 1981 and the www browser appeared in 1994. The browser was
the killer app for widespread adoption of the Internet. Prior to that
we discussed these issues on bulletin boards such as Compuserve via
circuit switched connections or early designs of packet switched
connections (Austpac in my case). I did not use TCP/IP or any special
protocol for Austpac, so it was presumably not the Internet as we know
it.
 
Re-wind a little, John. You told the guy "You must use NETBEUI" which
is 100% wrong.

I said "netbeui...can be used on a LAN in place of (or alongside)
tcp/ip". This is correct. I didn't say netbeui could be used over the
Internet.


Best you remain an end user then.


If you knew what you were talking about or bothered reading up a
little, you would know that "bog standard Windows" is already a smb
client and server without any third party functionality like NFS. It's
what you use when you drag and drop from windows explorer.


Jim.

Hello operator, I have a crossed line; someone from Mars is trying to
talk to me.
 
Back
Top