Hello,

Strange things are going on... computers can browse linux shared files,
through the local network ONLY when connected to the internet..
when the internet connection is closed.. it takes several minuites to
see inside the shared folder of the linux machine!

DETAILS:
I have set up a linspire box (LINUX) in a network with 5 other computers
that have windows xp and win98... This network has stiatic addresses,
XP main machine 192.168.0.1 and the rest 192.168.0.x

This XP machines is working as an internet connection share machine,
sharing is internet connection to the others.

On the Linux machine I have entered this info in the network configuration
window
of SAMBA

IP static 192.168.0.10
mask 255.255.255.0

Gateway 192.168.0.1 and DNS servers 192.168.0.1

Now when I was trying to browse the files from the XP machines to the linux
machine, it took ages.
For some other reason someone opened the internet connection and then the
folders could be browsed FAST!

Is it the extra gateway 192.168.0.1 and dns server settings I gave Linspire
the problem?
I would test this on that network, but its not my network and I will have
access to it in a few days..
I will have to know why this is happening!

I want the linspire box to work on the lan only.. no need for it to browse
the internet.

Has anybody seen this before????

Thanks in advance!

"John Jay Smith" <-> wrote:

What are the DNS settings on the XP machines? Why use ICS for Internet
sharing? It would be better to use a router. You can deny Linux access
to the Internet if you like.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

It does not make much sense that it would work only when the other computers
are on the internet. If you can get away from using ICS then I would
recommend doing such. The default gateway should not make any difference
since the computers are on the same network. I would use ping to verify
basic network connectivity between computers using both name an IP address
and try to access the computer share using the computer IP instead of name
in case there is some sort of name resolution problem. For instance in the
run box of the client computer you can use \\xxx.xxx.xxx.xxx or
\\xxx.xxx.xxx.xxx\sharename to try and access the computer with the shares
of course using the actual IP address of the server computer. The link
below may also help. If you are familiar with a packet sniffer like Ethereal
that can also help greatly in diagnosing networking problems. --- Steve

http://support.microsoft.com/default...;en-us;Q314067

"John Jay Smith" <-> wrote in message
news:ugNF7zDNGHA.2040@TK2MSFTNGP14.phx.gbl...

posting this for google group searchers.. YES indeed it was the gatway and
dns.

I removed them leaving only IP and MASK and it worked great!



--
Disclaimer: This info is given "as is".
If you do not like the content or attitude of my posts,
please put me on your ignore list or dont read my posts.

--
"John Jay Smith" <-> wrote in message
news:ugNF7zDNGHA.2040@TK2MSFTNGP14.phx.gbl...