Switch to Wifi broke network?

[newbi462]

did you check to make sure samba service is also set to start at boot time?

I set the "smb" to "at boot" no service called "samba" but that has to be it as SMB is what runs that

log in to root on the terminal and then run the following commands

service smb restart

[root@localhost omega]# service smb restart
Shutting down SMB services:                                                           [  OK  ]
Shutting down NMB services:                                                           [  OK  ]
Starting SMB services:                                                                [  OK  ]
Starting NMB services:                                                                [  OK  ]

smbtree -N -d2

wait for 10 seconds before issuing the second command and post the output of both

[root@localhost omega]# smbtree -N -d2
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
added interface wlan0 ip=fe80::218:39ff:fe07:76ae%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
added interface wlan0 ip=192.168.1.101 bcast=192.168.1.255 netmask=255.255.255.0
Got a positive name query response from 192.168.1.101 ( 192.168.1.101 )
Got a positive name query response from 192.168.1.101 ( 192.168.1.101 )
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
MDVGROUP
        \\LOCALHOST                     localhost
                \\LOCALHOST\Cups-PDF            Cups-PDF
                \\LOCALHOST\CANONBJC70_1        CANON MP530 FAX
                \\LOCALHOST\CANONBJC7000        CANON MP530
                \\LOCALHOST\IPC$                IPC Service (localhost)
                \\LOCALHOST\pdf-gen             PDF Generator (only valid users)
                \\LOCALHOST\print$
[root@localhost omega]#

[muungwana]

yes, the service is called "smb" but i keep refering to it as "samba" and thats what i write most of the time. Thanks for reminding me its "smb", not "samba" 

do you still have the problem?
Your linux box should now be in charge of the network and the output says the shares can successfully be seen.

"localhost" is not a good name to use over the network.

go through samba server configuration and set "netbios" name to something unique

[newbi462]

no it is not working...

trying to go to the shared folders and or system times out every time

I will wory about renaming groups after it works, for now just want to get to the folders on the Win box from the Linux box

trying to go to
smb://biggins/Videos/
or
smb://biggins/

just times out in dolphin every time

and smb://localhost/

renters file or folder does not exist

[muungwana]

"biggins" computer is not on the above list

what does "smbtree -d2 -N" give you now?

[newbi462]

"biggins" computer is not on the above list

"biggins" is the name of the windows system and should be its path. that is what it was before the change to wifi and on the windows system that is still the network path, but it is not showing up in SAMBA no mater where I click

what does "smbtree -d2 -N" give you now?

[root@localhost omega]# smbtree -d2 -N
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
added interface wlan0 ip=fe80::218:39ff:fe07:76ae%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
added interface wlan0 ip=192.168.1.101 bcast=192.168.1.255 netmask=255.255.255.0
Got a positive name query response from 192.168.1.101 ( 192.168.1.101 )
Got a positive name query response from 192.168.1.101 ( 192.168.1.101 )
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
WORKGROUP
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )
        \\BIGGINS
Error connecting to 66.152.109.110 (Success)
Error connecting to 69.16.143.110 (Success)
cli_start_connection: failed to connect to BIGGINS<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
MDVGROUP
        \\LOCALHOST                     localhost
                \\LOCALHOST\Cups-PDF            Cups-PDF
                \\LOCALHOST\CANONBJC70_1        CANON MP530 FAX
                \\LOCALHOST\CANONBJC7000        CANON MP530
                \\LOCALHOST\IPC$                IPC Service (localhost)
                \\LOCALHOST\pdf-gen             PDF Generator (only valid users)
                \\LOCALHOST\print$

[muungwana]

your results are not what i expect.

The problem is that samba local browser is running on a computer with address "192.168.1.101" but it is behind a firewall. The changes you made to linux where supposed to force linux to take over but now you seem to have both.
 
go to a computer with an IP address of "192.168.1.101" and configure its firewall to allow traffic on port 138,139 and 445 and then restart the computer.

when its up, wait for 3 minutes and then run the "smbtree" command and post your result

66.152.109.110

You keep getting this address because its still in its record,It should have expired by now. Your problem could also be here.You changed IP addresses when you moved from wired to wireless but that computer still has your computer on the wired interface.

It should take minutes( 15 samba docs say last time i checked) to update its list of computers and their shares.  ts taking days in your case

[newbi462]

the 192.168.1.101 is the PCLin box.... where would those port setting be?

[muungwana]

the 192.168.1.101 is the PCLin box.... where would those port setting be?

ok, in that case, i meant "open those ports on the computer with IP address of 192.168.1.103" 

What is going on is this,in a network, there should be only one computer that manages a list of all computers on the network and the resources they are sharing.

On your computer, you have two computer that is doing that.

Got a positive name query response from 192.168.1.101 ( 192.168.1.101 )
Got a positive name query response from 192.168.1.103 ( 192.168.1.103 )

The above two lines says two computers responded to a query of how many computers are on the network.

Error connecting to 66.152.109.110 (Success)

That lines says your computer tried to connect to a computer with that IP address because it was included in the query response. The .103 computers seem to be storing its records waaaaay past their limit. Is it a laptop computer? do you go out with it and connect to public internets?

cli_start_connection: failed to connect to BIGGINS<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL

Most people get this error when the computer that responded to the query is behind a firewall, This is the assumption i am operating with now.

BIGGINS runs on what operating system?

[newbi462]

BIGGINS is a windows Vista box and I have turned the Windows Firewall off... no third party one is running on that box so unless some windows service needs  to be killed? or tweaked?

only real change I made to the windows box is
http://www.techrepublic.com/article/get-vista-and-samba-to-work/6353849

By default Windows Vista sets the policy to "NTVLM2 responses only". Change this to "LM and NTLM – use NTLMV2 session security if negotiated".

Ya I agree it is acting like some fire wall is blocking things, but I kill the windows one, and as far as I know PClin dont do that? It is the same Wifi router I have always used a Liynksys G router

Both systems are towers, just I moved and where the router and computers need to be can not be in the same room in this place...

Literally just packed stuff, up moved it.... plugged the same router I have used for year in. Connected the PCLinux box using Wifi instead of Wired, and now they cannot see each other. It is just wierd...

[pags]

I still think that the wired and wireless networks sharing the same subnet (192.168.1.x) is not normal (unless the wireless router is acting as a bridge...since it seems to be an integral part of your wired network as well, I doubt it is bridging the two networks).

What is the make/model of your router, and what are the settings?

[newbi462]

I still think that the wired and wireless networks sharing the same subnet (192.168.1.x) is not normal (unless the wireless router is acting as a bridge...since it seems to be an integral part of your wired network as well, I doubt it is bridging the two networks).

how is that weird? I either plug a cable into one of the 4 ports on the back of it or connect by way of Wifi. Both ways the systems connect to the router and is dynamically assigned an IP by it. They are not 2 networks just one, every thing connects to the router.

What is the make/model of your router, and what are the settings?

It is a Linksys wrt54g
http://homesupport.cisco.com/en-us/support/routers/WRT54G

No real custom setting.... just set the network broadcast name and enabled WPA2 encryption on the wifi, oh and disabled remote access so people can not change its setting remotely... even with WPA2 I am paranoid 

[pags]

I don't know the WRT54G, but I would expect that the default settings would include a separation of wireless and wired, even if they can both access the Internet...this would be to prevent someone war-driving and accessing personal information on your wired network...

I would check the setting on the router...

Found this.  If this poster needed NETBUI to fix it, then it is a routing issue...

[newbi462]

I don't know the WRT54G, but I would expect that the default settings would include a separation of wireless and wired, even if they can both access the Internet...this would be to prevent someone war-driving and accessing personal information on your wired network...

then how did it work before when the Win Vista was on Wifi and the PClinux on Wired? It has always been a mixed network and all could always talk to each other

I would check the setting on the router...

Found this.  If this poster needed NETBUI to fix it, then it is a routing issue...

any thing in particular, like I said it worked fin before I moved the PClin to wifi that is litraly all that has changed, aside from the changes you asked me to make, the Win Vista has all ways been Wifi

[muungwana]

Try to give the wireless interface the same IP address the wired interface used to have and see if it will solve the problem.

[newbi462]

um it has always been 192.168.1.1 for both wired and wifi