samba Timeout worked last week?

[darkseed]

my smb tree looks like this

MSHOME
\\LINUX linux server (Samba, Ubuntu)
\\LINUX\ADMIN$ IPC Service (linux server (Samba, Ubuntu))
\\LINUX\IPC$ IPC Service (linux server (Samba, Ubuntu))
\\LINUX\print$ Printer Drivers
\\LAPPY dell
timeout connecting to 72.5.175.90:445
timeout connecting to 72.5.175.90:139
Error connecting to 72.5.175.90 (Operation already in progress)
cli_start_connection: failed to connect to LAPPY<20> (72.5.175.90)

ok first of all shouldnt my lappy ip be 192.168.1.100

if i go to remote places/samba shares i see my windows workgroup but i get a mshome timeout error

when i boot all 3 of my computers the smb tree looks like this

MSHOME
\\MASTERBLUE main
timeout connecting to 72.5.175.90:445
timeout connecting to 72.5.175.90:139
Error connecting to 72.5.175.90 (Operation already in progress)
cli_start_connection: failed to connect to MASTERBLUE<20> (72.5.175.90)
\\LINUX linux server (Samba, Ubuntu)
\\LINUX\ADMIN$ IPC Service (linux server (Samba, Ubuntu))
\\LINUX\IPC$ IPC Service (linux server (Samba, Ubuntu))
\\LINUX\print$ Printer Drivers
\\LAPPY dell
timeout connecting to 72.5.175.90:445
timeout connecting to 72.5.175.90:139
Error connecting to 72.5.175.90 (Operation already in progress)
cli_start_connection: failed to connect to LAPPY<20> (72.5.175.90)

have no clue why it was working last week
ive tried reinstalling 6.06 but error still there!!!

HElP!!!!!!!! please

[darkseed]

Re: samba Timeout worked last week?

i now can get into mshome and i can see my other machines but both windows shares timeout arrrgghhh

[wolfmaniac]

Re: samba Timeout worked last week?

ya i also faced same problem.
initially i was able to see my win xp box on samba but after a reboot i was even not able to ping both the boxes.

[Malden]

Re: samba Timeout worked last week?

Did you find any solution for this?
I am having the same problem. When using smbtree the PC name is found correctly but I also get something like

cli_start_connection: failed to connect to LAPPY<20> (72.5.175.90)

Looks like the connection fails because smbtree cannot resolve the correct IP address. I wonder where 72.5.175.90 comes from (in my case it's 62.something) which is actually not the one assigned to the Windows PC in the local network (192.168.x.x). An entry in /etc/hosts might help but what to do if the local IP addresses are automatically assigned via DHCP ?

This worked in Kubuntu 5.10, though.

Any ideas

Malden