This bug report is being closed due to your last comment regarding this
being fixed with a configuration change. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can
Hi,
In Gutsy, the problem was solved by using specific IP addresses. In
Hardy same behaviour. I think it was a fundemental change in SAMBA, but
I've figured it out. Guess you can close this one off.
Thanks
--
Gutsy cannot connect to Windows Network
https://bugs.launchpad.net/bugs/183037
You
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release?
If you are still having this problem, i
Yes, "Chuck Short" is correct (I think). It appears that Firestarter &
Gutsy have some issues.
Is there a workaround?
--
Gutsy cannot connect to Windows Network
https://bugs.launchpad.net/bugs/183037
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
This is more of a firewall issue than a samba issue.
** Changed in: firestarter (Ubuntu)
Sourcepackagename: samba => firestarter
--
Gutsy cannot connect to Windows Network
https://bugs.launchpad.net/bugs/183037
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same behavior on one of my gutsy boxes at home.
Place, Network, Windows Network, workgroup_name, computer name generated the
error
Adding to /etc/hosts
192.168.20.4 computer_name
gave me access to SharedDocs
Curiously browsing from the Windows XP machine worked so XP could connect
without name
Sorry, I should say Firestarter locked out NetBIOS names, but not
specific IP addresses. Don't know how to change this parameter. Seems
several people have this issue.
--
Gutsy cannot connect to Windows Network
https://bugs.launchpad.net/bugs/183037
You received this bug notification because yo
Did a lot of investigation with the help of EVANCHU. The details of
how is at Ubuntu Forums post is here:
http://ubuntuforums.org/showthread.php?p=4150905#post4150905
Basically, I think FIRESTARTER tweaked the iptables somehow on the
first run and locked out SAMBA as a default. Allowing SAMBA
You are saying that you can't connect using a hostname to another windows
computer? This works fine for me with the default setup.
What changes have you made? Do you get this same behavior with the liveCD?
Also, please describe a little about how your network is setup.
** Changed in: samba (
Update: I tried IP addresses and they work fine. Gutsy has no problems
with IP addresses - can't seem to utilise domain names. Indicates that
SAMBA is correctly operating but not transparent.user friendly as was
the default in Feisty.
Q: Is a package missing? Or is this a regression?
--
Guts
10 matches
Mail list logo
