Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

help w/ red hat and winxp networking

Status
Not open for further replies.

ThePug

Technical User
Jun 22, 2003
24
US
hi all!
i have a winxp PC and a red hat 9 PC. both connected to the internet thru a linksys router. the red hat9 PC has 3 HD's each 6 gig in size. 2 of the HD i formatted as fat32.

what im trying to do is do file sharing between red hat and winxp with the HD in the linux machine formatted as fat32.

i mounted the fat32 drive then used samba to share the drive(hdb1). the win xp mahine can see the samba server but once i click it a message appears:

\\localhost is not accessible. you might not have permission to use this network resource.

you were not connected because a duplicate name exist on the network.

what am i missing? the red hat firewall is set to high with DHCP the only one checked.

thanks!



 
My guess is that samba did a broadcast of its shares that the XP machine caught and cached. Now, when you see the "share" on the WinXP box, you are seeing the advertisement in the cache.

I would suspect that your firewall setting is preventing the access test that is generating the error. The notation of "\\localhost" tells me that the WinXP box is guessing wildly at where the heck to find the share. I ASSUME THAT YOU HAVE NOT USED THE SAME HOSTNAME on both boxen.

RedHat's firewall configurator should allow you to open up access to the shares. Remember, your WinXP box need to initiate the "conversation" to start the share. Without exposing the samba port(s) to open access you won't get very far.

"Surfinbox Shares" - A fundraising program that builds revenue from dialup Internet users.
 
hi! thanks for replying.

i did the same workgroup name. ahm, is that the same as hostname?

what other options should i check on the firewall? should i set eth0 to trusted?

one more thing would mandrake be easier? thanks![afro2]
 
hostname is the name you give the machine it is usually assigned to eth0 and an ip address . All machines think their name is localhost but is usually just assigned to the loopback device (lo)which has the ip of 127.0.0.1. It is a safe guess that your machines have not been assigned a unique host name.
 
In windows, you define the machine with both a machine name and a workgroup name. In samba/linus this is equiv. to samba workgroup and hostname.

Example that should resolve your issue:
(I forget if Samba allows you to define a samba hostname, which might sufficient)

WinXP:
Machine = Host1
Workgroup = Brewing

Linux:
Machine = Host2.example.com or host2
Workgroup (defined in samba config file) = Brewing

The sameness of the workgroup allows Win and Samba to send broadcasts to the workgroup.
The uniqueness of the hostname let's them keep each other distinct.
DO NOT use 'localhost' for either machine's host/machine name


"Surfinbox Shares" - A fundraising program that builds revenue from dialup Internet users.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top