Samba not working properly

JohnU

When I have my internet connection plugged in to the internet port on my Linksys WRT56G router I cannot mount Samba shares with either of my windowsXP computers. When I unplug the internet from the router I can mount both of the other computers and transfer files normally, both wirelessly and wired. What the heck is causing this issue? Everything else works normally wirelessly (TiVo, 360, Wii, notebook and HTPC) so this is the only issue I have, any help greatly appreciated.

Thanks!

Lusankya

As much as it sounds like a problem with the router, I'm leaning towards pinning the blame on the Linux box. Samba doesn't play nice with anything until you break it in. However, before I tell you to go ripping apart your smb.conf, check the Linux box's IP address. If DHCP is off in the router, or the Linux box is in the DMZ, that could very well cause the issues.

Answer these questions, and we'll have a better idea of where you stand:
1) Are all machines assigned to the same Windows workgroup?
2) Is DHCP on in the router?
3) Are there any machines assigned to the DMZ in the router?
4) With the router WAN port unplugged, do all machines have 192.168.1.x IPs?
5) With the WAN port connected and all machines rebooted, do all machines still have 192.168.1.x IPs?
6) Can you see the Linux box from a Windows machine with ping?
7) Does issuing "sudo /etc/init.d/samba stop" on the box with the Samba share generate an error?

EDIT: Last I remember, Linksys routers use 1 as the default C (third) level IP address. As long as all the addresses start with 192.168, and the C block is the same on all computers, it doesn't matter what number it uses.

Apreche

It's probably a DNS issue. When your Internet connection is working, your computers are resolving against your ISPs DNS server. When your Internet connection is down, they are resolving via some other means.

JohnU

Answer these questions, and we'll have a better idea of where you stand:
1) Are all machines assigned to the same Windows workgroup?
2) Is DHCP on in the router?
3) Are there any machines assigned to the DMZ in the router?
4) With the router WAN port unplugged, do all machines have 192.168.1.x IPs?
5) With the WAN port connected and all machines rebooted, do all machines still have 192.168.1.x IPs?
6) Can you see the Linux box from a Windows machine with ping?
7) Does issuing "sudo /etc/init.d/samba stop" on the box with the Samba share generate an error?

1. The two Windows computers are both part of MSHOME, which I can see when the internet is connected to the router, just not mount anything.
2. I am using static IP.
3. DMZ is disabled.
4. Yes, at least I think they do . . .
5. see #4.
6. The windows laptop succesfully pinged the Linux box with the internet connection plugged into the router.
7. Nope, it says "Stopping Samba daemons"

Wow, thanks for the quick and indepth response. I hope my replies make some kind of sense.

Lusankya

It's probably a DNS issue. When your Internet connection is working, your computers are resolving against your ISPs DNS server. When your Internet connection is down, they are resolving via some other means.

2. I am using static IP.

I see what you did there. I bet that the IP you have mapped to your Linux box is in use by your ISP somewhere else on the network. Your machines are asking the ISP's DNS server for directions to Oregon, and the ISP is sending them to the country instead of the state. Try using DHCP, or change the static IPs to something that shouldn't be in use. Your ISP's DNS should never resolve IP's from the 192 A block, so try setting your statics to 192.B.C.D.

JohnU

I bet that the IP you have mapped to your Linux box is in use by your ISP somewhere else on the network. Your machines are asking the ISP's DNS server for directions to Oregon, and the ISP is sending them to the country instead of the state. Try using DHCP, or change the static IPs to something that shouldn't be in use. Your ISP's DNS should never resolve IP's from the 192 A block, so try setting your statics to 192.B.C.D.

I can't use DHCP so I guess I will have to change the static IPs. Is changing the statics to 192.B.C.D is something I need to do in the router settings? Also, what would a 192.B.C.D address look like versus 192.168.1.102?

CHOIS CHOIS CHOIS

It's probably because Nintendo dosen't care about you, or it's some friend code BS issue.

Tyashki

Did you even read the question?

ColdfireSerge

It's probably because Nintendo dosen't care about you, or it's some friend code BS issue.

While I have read about at least one person talking about their problems with the new Samba de Amigo game today, this topic appears to be entirely different. None-the-less your confusion is amusing. I thought the same when I clicked the thread title.
I have nothing useful to add to the real topic at hand, however.

Lusankya

I can't use DHCP

Any reason why not? If you need to consistently have the same IP address on certain machines, you should use static DHCP. It should eliminate all this trouble.

Also, what would a 192.B.C.D address look like versus 192.168.1.102?

You've got it spot on. B, C and D are variables you can set yourself (if you want to get technical, B should be set to 168 to be IANA compliant, but your ISP most likely just turfs all DNS requests for 192 A block addresses.)

If you're still having trouble, try using 192.168.196.D (or anything that's not 0, 1, 5, 10, 100 or 200; these are the most popular C blocks) for your IPs. If you don't have a dedicated line to your ISP and your neighbor sucks at setting up his/her home network, your PCs may be trying to resolve your IPs on someone else's network.