Networking XP with Linux box

[Hiawatha Bray]

I have a Linux computer on the same network as a Windows XP machine. The
Linux computer automatically recognizes the presence of the Windows
computer, allowing for file sharing. But the Windows machine doesn't see
the Linux machine. How can I fix this? Thanks.

 

[New Guy]

I have a Linux computer on the same network as a Windows XP machine. The
Linux computer automatically recognizes the presence of the Windows
computer, allowing for file sharing. But the Windows machine doesn't see
the Linux machine. How can I fix this? Thanks.

Samba

 

[Ivan Filpo]

They both belong to the same workgroup? That may be the problem, just like
different subnet masks.

 

[ray]

I have a Linux computer on the same network as a Windows XP machine. The
Linux computer automatically recognizes the presence of the Windows
computer, allowing for file sharing. But the Windows machine doesn't see
the Linux machine. How can I fix this? Thanks.

samba

 

[SpongeBob SquarePants]

As mentioned - SAMBA

--
"SpongeBob SquarePants"
"Who lives in a pineapple under the sea?"

Small Note: If you want to learn how to fix/do something, I'll point you to
it, but if you want me to do your work for you, it will cost you $50 USD per
hour - your choice.

 

[p cooper]

Im struggling with this as well.
Gentoo Linux server running samba 2.2.8 and Win XP Home

'view Workgroup Computers' sees the router but when i try to open it I
get
\\Router is not accessible.You might not have permission to use this
network resource .......
You were not connected because a duplicate name exists on the network
......."

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\PAUL>net view
Server Name Remark
-------------------------------------------------------------------------------
\\DADSLAPTOP dadslaptop
\\DATA The one with the big disk
\\NEVADA Fileserver
\\POOTER
\\ROUTER Router(Samba Server 2.2.8a)
The command completed successfully.
C:\DOCUME~1\PAUL>

My Network places -> disconnect network drive says 'no network drives
connected'

my computer -> Map network drive brings up the list of shares but i
get the same message when trying to connect.

no idea whih computer name it thinks is duplicate and why it wont let
me connect
Is it actually possibel to connect WInXP Home to Samba ?

 

[Hiawatha Bray]

I don't understand. Obviously Samba's running on the Linux box; that's why
it shows me the Windows machine. My problem is that the Linux box does NOT
appear in my Windows network directory. Any idea how to fix this?

 

[Hiawatha Bray]

How do I check this? Thanks.

They both belong to the same workgroup? That may be the problem, just like
different subnet masks.

 

[Peter =?ISO-8859-15?Q?K=F6hlmann?=]

I don't understand. Obviously Samba's running on the Linux box; that's
why
it shows me the Windows machine. My problem is that the Linux box does
NOT
appear in my Windows network directory. Any idea how to fix this?

First of all: Don't top-post

Second: Samba

You have smbclient running, so you can see SMB shares on the network.
To make your linux machine appear on the network as a server, install the
samba-server

< snip bottom quote >

 

[Rick \Nutcase\ Rogers]

A. Because no one wants to scroll through old messages to get to the new one
in a thread. If everyone just responds to the original thread instead of
starting a new one, there is no need to read through all the prior posts to
get to the new information.
Q. Why is top posting becoming the norm or at least just as acceptable as
bottom posting?

A. Because they refuse to accept that usenet is no longer just for the
geeks. Times change, usenet needs to change with it.
Q. Why do some still insist that everyone bottom post?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Joe]

I have a Linux computer on the same network as a Windows XP machine. The
Linux computer automatically recognizes the presence of the Windows
computer, allowing for file sharing. But the Windows machine doesn't see
the Linux machine. How can I fix this? Thanks.

From what I've seen in the rest of the posts, it appears that you may have
samba running but that's not enough. You have to edit the configuration
file smb.conf. Or you can use SWAT (Samba Web Administration Tool).
Depending on your firewall and your smb.conf settings you should be able to
access SWAT by typing the following into a web browser on the same network:
<IP address of Linux box>: 901. Include the colon between the 901 and the
IP address. Also, check the configuration of your firwall; if you're
running a firewall on either machine it could be interfering with the
required ports to establish an smb connection. To connect to a Samba share
the user must have an account on the Linux machine.
This is all basic stuff if you've studied any of the SAMBA documentation
(man samba). I believe there's also a configuration utility if you're using
the graphical interface in Linux. Start reading my friend, you have a long
way to go. Try the how-tos at justlinux.com.

Joe

 

[Hiawatha Bray]

At last...an answer with information in it! This is most helpful. Now I
know where to start looking. Thanks much!

 

[Shenan Stanley]

I have a Linux computer on the same network as a Windows XP
machine. The Linux computer automatically recognizes the presence
of the Windows computer, allowing for file sharing. But the
Windows machine doesn't see the Linux machine. How can I fix this?
Thanks.

From what I've seen in the rest of the posts, it appears that you
may have samba running but that's not enough. You have to edit the
configuration file smb.conf. Or you can use SWAT (Samba Web
Administration Tool). Depending on your firewall and your smb.conf
settings you should be able to
access SWAT by typing the following into a web browser on the same
network:
<IP address of Linux box>: 901. Include the colon between the 901
and the IP address. Also, check the configuration of your firwall;
if you're running a firewall on either machine it could be
interfering with the required ports to establish an smb connection. To
connect to a Samba share
the user must have an account on the Linux machine.
This is all basic stuff if you've studied any of the SAMBA
documentation (man samba). I believe there's also a configuration
utility if you're using
the graphical interface in Linux. Start reading my friend, you have
a long way to go. Try the how-tos at justlinux.com.

At last...an answer with information in it! This is most helpful. Now I
know where to start looking. Thanks much!

So essentially, you needed a RTFM response?

 

[Timothy Daniels]

So essentially, you needed a RTFM response?

Hey! Some of us don't have Linux, yet, and
some of us don't have Samba, yet, either,
but it's good information to have for the future.
Usenet isn't just for people confronted with an
immediate problem.

*TimDaniels*

 

[Shenan Stanley]

At last...an answer with information in it!
This is most helpful. Now I know where
to start looking. Thanks much!

So essentially, you needed a RTFM response?

Hey! Some of us don't have Linux, yet, and
some of us don't have Samba, yet, either,
but it's good information to have for the future.
Usenet isn't just for people confronted with an
immediate problem.

What does thast have to do with reading the manuals and searching with tools
like Google for your answers?

 

[Bit Twister]

Usenet isn't just for people confronted with an
immediate problem.

It is not a personal helpdesk either.
You may want to read


Do bookmark the following, very large,
Frequently Asked Questions (faq) Search engine:

http://groups.google.com/advanced_group_search
key word(s) in the first box
*linux* in Newsgroup box. You need to use the two
asterisks around linux, pick English

 

[Enkidu]

Hey! Some of us don't have Linux, yet, and
some of us don't have Samba, yet, either,
but it's good information to have for the future.
Usenet isn't just for people confronted with an
immediate problem.

Almost every package has a Home Page. Also you can find plenty of
user-space information about the packages online - such as how to
install the packages and so on. Every package comes with documentation
- admittedly it's often terse and a little inpenetrable. It's a little
lazy not to do the research first.

Cheers,

Cliff

 

[Timothy Daniels]

It is not a personal helpdesk either.

Well don't answer, then, if you find it a burden.

*TimDaniels*

 

[Bit Twister]

Well don't answer, then, if you find it a burden.

Sorry you did not read the smart question link.

 

[Hiawatha Bray]

This argument makes as much sense as saying that reading manuals is
lazy. After all, a real geek could simply dig out the source code and
analyze it line by line to get an answer. A proper manual--and hardly
any man page fits this definition--is supposed to provide quick
answers to basic questions. By your apparent standards, this
expectation marks me as lazy. No problem. I'm all for laziness, if
all you want is to get a question answered so you can get back to your
real work.

And so we come to Usenet, a place where I and many others routinely go
to ask quick questions of people who already know the answers. And
here's a shock--most people think this is a perfectly sensible thing
to do. Consider the Microsoft.public newsgroups, where
MVPs--Microsoft-certified experts on various Microsoft apps--hang out
for the express purpose of fielding such questions. Nobody at a
Microsoft.public group considers it bad form to ask a casual question.
The same holds at thousands of other newsgroups.

Come to think of it, the same applies to many people here. Only a
handful, like yourself, do not wish to be bothered. Which raises a
rather obvious point--why did you bother? You're under no obligation
whatever to respond to messages you consider a waste of time. So next
time you see one of them, simply pass it by.