Ubuntu

Cannot access to local network.

Asked by Ben Sykes

Hi I've been having problems accessing my local network from ubuntu 7.10. The system is happily sharing files with other windows pc's on my network and up until a recent re-installation (on the ubuntu machine) I was able to see the network as well. Now I can't even see the files that I am sharing over the network, even though they are obviously sharing fine. When I try to access the network from nautilus (smb:///) it shows me the mshome workgroup (which is the only workgroup being used), when I click it it gives me this error message:

"The folder contents could not be displayed.
Sorry, couldn't display all the contents of "Windows Network: mshome". "

and I get a blank screen.

The read out from smbtree in the terminal is this:

"
ben@the-bishop:~$ smbtree
Password:
MSHOME
        \\THE-BISHOP the-bishop server (Samba, Ubuntu)
Error connecting to 195.238.237.143 (Connection refused)
cli_start_connection: failed to connect to THE-BISHOP<20> (195.238.237.143). Error NT_STATUS_CONNECTION_REFUSED
        \\HOLLY mikes laptop
Error connecting to 195.238.237.143 (Connection refused)
cli_start_connection: failed to connect to HOLLY<20> (195.238.237.143). Error NT_STATUS_CONNECTION_REFUSED
ben@the-bishop:~$
"

the-bishop is the ubuntu and holly is the windows pc.
Any help would be greatly appreciated as I have no idea why I cannot access them any more from the clean install.

Thanks
Ben

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Ben Sykes
Solved:
Last query:
Last reply:
Revision history for this message
Ben Sykes (bensykes55) said : 		#1

Another readout. Konqueror says:

"Timeout on server
mshome"

Ben

Revision history for this message
Ben Sykes (bensykes55) said : 		#2

Hi again, I thought perhaps the nautilus readout might be useful.

sudo nautilus network:///
Initializing gnome-mount extension
Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

The first error readout came as soon as nautilus ran, the rest came after I'd clicked "Windows Network"

Thanks
Ben