Hello
In my organization we are running samba 2.0.7 for 1 month in
Solaris 8 machines, with clients windows 95 and 98.
The problem is that the last week whe changed the configuration of
the clients to DHCP. Clients receive their IP address, DNS and WINS servers
for DHCP. And, with this change, the clients need some time to see the
samba server, and when try to connect automatically to the shares, they
can't contact the server, and give errors.
And it's a big problem, since people who work with clients
don't
know how to connect to samba shares manually, and need help to start
working as usually.
We've tried changing to a fix WINS server address, and the problem
disappears and all works perfect, but we are interested to work with WINS
served by DHCP.
We've tried much things, and nothing works.
Can you help me? We are hopeless!
Thanks!
On Fri, 1 Dec 2000, Angel Ramon wrote:> We've tried changing to a fix WINS server address, and the problem > disappears and all works perfect, but we are interested to work with WINS > served by DHCP.We run with all clients DHCPed, including DNS and WINS addresses with no problems. I assume the WINS server addresses you are giving through DHCP are the same as you are testing the fixed WINS address? check a client just after boot and do an "ipconfig /all" or winipconfig and check that the wins and DNS addresses are showing up correctly. Add the samba server as a static entry in WINS. Check that if you have multiple WINS servers they are synced. Good luck. -- David A. Smith dasb@eci.esys.com Systems Administrator, Raytheon Systems St. Petersburg, FL 727-302-3202 fax 727-302-3408
Yes, we try with the same WINS servers dinamically and statically. And the same machine is Wins Server, Samba server and DHCP server! It's very strange... I'm going to sync the other wins server, but I think they are yet. Thanks, and if you have other ideas... ********************** At 07:59 1/12/00 -0500, you wrote: On Fri, 1 Dec 2000, Angel Ramon wrote: > We've tried changing to a fix WINS server address, and the problem > disappears and all works perfect, but we are interested to work with WINS > served by DHCP. We run with all clients DHCPed, including DNS and WINS addresses with no problems. I assume the WINS server addresses you are giving through DHCP are the same as you are testing the fixed WINS address? check a client just after boot and do an "ipconfig /all" or winipconfig and check that the wins and DNS addresses are showing up correctly. Add the samba server as a static entry in WINS. Check that if you have multiple WINS servers they are synced. Good luck. -- David A. Smith dasb@eci.esys.com Systems Administrator, Raytheon Systems St. Petersburg, FL 727-302-3202 fax 727-302-3408
goodday! i think it is a windoze problem, it seems like if you set new network parameters via dhcp you have to do ipconfig /renew_all to windoze clients. maybe it is not true in your situation but it certainly is in our lab, and me thinks it [windoze dhcp client behavoir] was mentioned in 'dhcp handbook' mabuhay!, barryg On Fri, Dec 01, 2000 at 01:33:54PM +0100, Angel Ramon wrote:> > Hello > > In my organization we are running samba 2.0.7 for 1 month in > Solaris 8 machines, with clients windows 95 and 98. > > The problem is that the last week whe changed the configuration of > the clients to DHCP. Clients receive their IP address, DNS and WINS servers > for DHCP. And, with this change, the clients need some time to see the > samba server, and when try to connect automatically to the shares, they > can't contact the server, and give errors. > And it's a big problem, since people who work with clients don't > know how to connect to samba shares manually, and need help to start > working as usually. > We've tried changing to a fix WINS server address, and the problem > disappears and all works perfect, but we are interested to work with WINS > served by DHCP. > > We've tried much things, and nothing works. > > Can you help me? We are hopeless! > > Thanks!
You should have a fixed wins server. That is the problem. Your DHCP server should tell the clients where the wins server is located. It cant if it changes all the time. -----Original Message----- From: Barry Dexter A. Gonzaga [mailto:barryg@tasyo.kssp.upd.edu.ph] Sent: Saturday, December 02, 2000 8:48 AM To: samba@us5.samba.org Subject: Re: Problem with DHCP goodday! i think it is a windoze problem, it seems like if you set new network parameters via dhcp you have to do ipconfig /renew_all to windoze clients. maybe it is not true in your situation but it certainly is in our lab, and me thinks it [windoze dhcp client behavoir] was mentioned in 'dhcp handbook' mabuhay!, barryg On Fri, Dec 01, 2000 at 01:33:54PM +0100, Angel Ramon wrote:> > Hello > > In my organization we are running samba 2.0.7 for 1 month in > Solaris 8 machines, with clients windows 95 and 98. > > The problem is that the last week whe changed the configurationof> the clients to DHCP. Clients receive their IP address, DNS and WINSservers> for DHCP. And, with this change, the clients need some time to see the > samba server, and when try to connect automatically to the shares, they > can't contact the server, and give errors. > And it's a big problem, since people who work with clients don't > know how to connect to samba shares manually, and need help to start > working as usually. > We've tried changing to a fix WINS server address, and theproblem> disappears and all works perfect, but we are interested to work with WINS > served by DHCP. > > We've tried much things, and nothing works. > > Can you help me? We are hopeless! > > Thanks!
At 07:47 2/12/00 -0800, you wrote:>goodday! > >i think it is a windoze problem, it seems like if you set new network >parameters via dhcp you have to do ipconfig /renew_all to windoze >clients. maybe it is not true in your situation but it certainly is in >our lab, and me thinks it [windoze dhcp client behavoir] was mentioned >in 'dhcp handbook' > >mabuhay!, barryg > >On Fri, Dec 01, 2000 at 01:33:54PM +0100, Angel Ramon wrote: > > > > Hello > > > > In my organization we are running samba 2.0.7 for 1 month in > > Solaris 8 machines, with clients windows 95 and 98. > > > > The problem is that the last week whe changed the > configuration of > > the clients to DHCP. Clients receive their IP address, DNS and WINS > servers > > for DHCP. And, with this change, the clients need some time to see the > > samba server, and when try to connect automatically to the shares, they > > can't contact the server, and give errors. > > And it's a big problem, since people who work with clients don't > > know how to connect to samba shares manually, and need help to start > > working as usually. > > We've tried changing to a fix WINS server address, and the > problem > > disappears and all works perfect, but we are interested to work with WINS > > served by DHCP. > > > > We've tried much things, and nothing works. > > > > Can you help me? We are hopeless! > > > > Thanks!
And what is the DHCP handbook? Where can i find it, please? At 07:47 2/12/00 -0800, you wrote: goodday! i think it is a windoze problem, it seems like if you set new network parameters via dhcp you have to do ipconfig /renew_all to windoze clients. maybe it is not true in your situation but it certainly is in our lab, and me thinks it [windoze dhcp client behavoir] was mentioned in 'dhcp handbook' mabuhay!, barryg On Fri, Dec 01, 2000 at 01:33:54PM +0100, Angel Ramon wrote: > > Hello > > In my organization we are running samba 2.0.7 for 1 month in > Solaris 8 machines, with clients windows 95 and 98. > > The problem is that the last week whe changed the configuration of > the clients to DHCP. Clients receive their IP address, DNS and WINS servers > for DHCP. And, with this change, the clients need some time to see the > samba server, and when try to connect automatically to the shares, they > can't contact the server, and give errors. > And it's a big problem, since people who work with clients don't > know how to connect to samba shares manually, and need help to start > working as usually. > We've tried changing to a fix WINS server address, and the problem > disappears and all works perfect, but we are interested to work with WINS > served by DHCP. > > We've tried much things, and nothing works. > > Can you help me? We are hopeless! > > Thanks!