Re: Win95 Dialin Client Config

1998-03-02 Thread Ronn Pimentel

Wins is: (from the Wins Help file)
A WINS server is a WindowsNT Server computer running Microsoft TCP/IP and
the Windows Internet Name Service (WINS) server software. WINS servers
maintain a database that maps computer names to TCP/IP addresses, allowing
users to easily communicate with other computers while gaining all the
benefits of TCP/IP.



On Sun, 1 Mar 1998, Erez Doron wrote:

 
 
 Ronn Pimentel wrote:
 
  First you want to make sure the the WINS server is running.
 
 [major snip]What is a WINS server ?is it anything to do with samba ?
 
 Regards
 Erez
 
 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Win95 Dialin Client Config

1998-03-01 Thread Erez Doron


Ronn Pimentel wrote:

 First you want to make sure the the WINS server is running.

[major snip]What is a WINS server ?is it anything to do with samba ?

Regards
Erez

begin:  vcard
fn: Erez Doron
n:  Doron;Erez
org:Savan Communications Ltd.
email;internet: [EMAIL PROTECTED]
title:  Asic/Software/Sysadmin
x-mozilla-cpt:  ;0
x-mozilla-html: TRUE
version:2.1
end:vcard



Re: Win95 Dialin Client Config

1998-03-01 Thread Glynn Clements

Erez Doron wrote:

  First you want to make sure the the WINS server is running.
 
 [major snip]What is a WINS server ?is it anything to do with samba ?

WINS = Windows Internet Name Service

Basically it's a NetBIOS name resolution mechanism, i.e. it translates 
NetBIOS names (the host part of \\host\share) into network addresses.

-- 
Glynn Clements [EMAIL PROTECTED]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Win95 Dialin Client Config

1998-02-27 Thread Ronn Pimentel


First you want to make sure the the WINS server is running.  I've had
plenty of experiences where WINS just died for no apparent reason.

Next make sure in DUN that they specify the WINS server(s) in the TCP/IP
config.

Next make sure that they have Logon to Network in DUN checked.  This way
they logon to the WinNT Domain and have all the rights and permissions
as if they were on the local LAN.



On Thu, 26 Feb 1998, Kevin Traas wrote:

 Here at work, I've installed a Linux box with a couple of modems hanging off
 it for dialin access for remote users.  Everyone can dialin and access the
 network, etc.  except that there's one little problem that I haven't been
 able to find any docs / info about
 
 None of these dialin users (Win95 or WinNT WS) can browse the network
 using Network Neighborhood.  They get a Can't Browse Network message.
 However, everything else works fine.  I've got a WINS server running and the
 Linux is a DNS server, so name resolution isn't a problem.  However, they
 can't use the Network Neighborhood to browse to a server, connect a share,
 etc.
 
 Anyone have any ideas on how to get this configured and working?  I'd really
 like to get it working because, well, I'm the one with a bit on the line in
 suggesting using the Linux box to manage remote dialin users.  Now, people
 are starting to ask why we're not using RAS instead?
 
 My thoughts are because it only runs on NT and Microsoft made it...
 grin... but the people on my end aren't seeing these as good reasons
 
 TIA,
 Kevin Traas
 
 
 --
 TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
 [EMAIL PROTECTED] . 
 Trouble?  e-mail to [EMAIL PROTECTED] .
 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Win95 Dialin Client Config

1998-02-27 Thread Thomas Lakofski
On Thu, 26 Feb 1998, Kevin Traas wrote:

 None of these dialin users (Win95 or WinNT WS) can browse the network
 using Network Neighborhood.  They get a Can't Browse Network message.
 However, everything else works fine.  I've got a WINS server running and the
 Linux is a DNS server, so name resolution isn't a problem.  However, they
 can't use the Network Neighborhood to browse to a server, connect a share,
 etc.

If you take a look at /etc/ppp/options you can specify a 'wins-addr'
option which should give your win95 dialup clients the right WINS
addresses.  Last time I checked NT had some problems with getting the
assignment, but that might have changed since I last used it (about 1 year
ago).  You can also specify the dns addresses in a similar manner -- take
a look at the file.  The advice given in a follow-up to your email about
having the clients log on to the NT domain is also correct (as is the rest
of it -- this might just help make things smoother).

Thomas.


M$ slips up in true Freudian style...
Seminar attendee: Why is [Outlook] so slow?
M$ rep:   That's because it's live on the network.
Seminar attendee: As opposed to...?
Stop the madness!  Free yourselves!  http://www.opensource.org/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Win95 Dialin Client Config

1998-02-27 Thread Kevin Traas
 None of these dialin users (Win95 or WinNT WS) can browse the network
 using Network Neighborhood.  They get a Can't Browse Network message.
 However, everything else works fine.  I've got a WINS server running and
the
 Linux is a DNS server, so name resolution isn't a problem.  However, they
 can't use the Network Neighborhood to browse to a server, connect a
share,
 etc.

If you take a look at /etc/ppp/options you can specify a 'wins-addr'
option which should give your win95 dialup clients the right WINS
addresses.  Last time I checked NT had some problems with getting the
assignment, but that might have changed since I last used it (about 1 year
ago).  You can also specify the dns addresses in a similar manner -- take
a look at the file.  The advice given in a follow-up to your email about
having the clients log on to the NT domain is also correct (as is the rest
of it -- this might just help make things smoother).


Thanks for the comments.  My apologies for not providing enough information.

I do have everything set properly as mentioned above.  The Win95 clients
have the Log onto Network option checked and running winipcfg on them
reveals that DNS, WINS, IP, Mask, Gw, etc. are all configured as expected.

Any other suggestions?

Regards,
Kevin Traas


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Win95 Dialin Client Config

1998-02-27 Thread Thomas Lakofski
On Thu, 26 Feb 1998, Kevin Traas wrote:

 Thanks for the comments.  My apologies for not providing enough information.
 
 I do have everything set properly as mentioned above.  The Win95 clients
 have the Log onto Network option checked and running winipcfg on them
 reveals that DNS, WINS, IP, Mask, Gw, etc. are all configured as expected.
 
 Any other suggestions?

ummm, I'll put on my MCSE hat (blush) and say: try rebuilding the WINS
database, check that browsing works with an NT RAS server, and not with
Debian... errr, beyond that, I can only say that it's why I'm not a
practising MCSE (even though the 'exams' i had to take were a complete
joke...)

(sorry for the off-topic-ness)

Thomas.


M$ slips up in true Freudian style...
Seminar attendee: Why is [Outlook] so slow?
M$ rep:   That's because it's live on the network.
Seminar attendee: As opposed to...?
Stop the madness!  Free yourselves!  http://www.opensource.org/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Win95 Dialin Client Config

1998-02-27 Thread Ronn Pimentel


On Thu, 26 Feb 1998, Kevin Traas wrote:

 Thanks for the comments.  My apologies for not providing enough information.
 
 I do have everything set properly as mentioned above.  The Win95 clients
 have the Log onto Network option checked and running winipcfg on them
 reveals that DNS, WINS, IP, Mask, Gw, etc. are all configured as expected.
 
 Any other suggestions?
 

If the people are logging in with laptops, try removing the ethernet card.
And then when the machine comes up with the login screen hit Cancel, and
then try logging in via DUN.  Which version of Win95?  Original, A, or
OemB, crispy, extra crispy, with or without IE4?  (Sorry so many versions 
to keep track of).

Worst case scenerio, goto the windows directory and remove the .PWL files
and restart the computer and try the above.  This has worked from time to
time for me.  

--
[EMAIL PROTECTED]
Whatever


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


RE: Win95 Dialin Client Config

1998-02-27 Thread Thomas Heide Clausen
-BEGIN PGP SIGNED MESSAGE-

I would look at SAMBA (http://samba.anu.edu.au/samba/). I have
set it up succesfully under many UNIX flavours, and it works
like a dream (allmost out of the box).

Cheers, and good luck.

- --thomas

ps: What is the WINS you're talking about? Sone NIS derivation?

On 26-Feb-98 Kevin Traas wrote:
 Here at work, I've installed a Linux box with a couple of
 modems hanging off
 it for dialin access for remote users.  Everyone can dialin
 and access the
 network, etc.  except that there's one little problem that I
 haven't been
 able to find any docs / info about
 
 None of these dialin users (Win95 or WinNT WS) can browse
 the network
 using Network Neighborhood.  They get a Can't Browse
 Network message.
 However, everything else works fine.  I've got a WINS server
 running and the
 Linux is a DNS server, so name resolution isn't a problem. 
 However, they
 can't use the Network Neighborhood to browse to a server,
 connect a share,
 etc.
 
 Anyone have any ideas on how to get this configured and
 working?  I'd really
 like to get it working because, well, I'm the one with a bit
 on the line in
 suggesting using the Linux box to manage remote dialin users. 
 Now, people
 are starting to ask why we're not using RAS instead?
 
 My thoughts are because it only runs on NT and Microsoft
 made it...
 grin... but the people on my end aren't seeing these as good
 reasons
 
 TIA,
 Kevin Traas
 
 -
 To unsubscribe from this list: send the line unsubscribe
 linux-net in
 the body of a message to [EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: 2.6.3ia
Charset: noconv

iQCVAwUBNPXSx8QLb2bL5bWVAQFDWAQAx6JsJkJVYRL5yp6MkmvV/gHRyFwRGjfh
TG+aITaME9NVWFwmKXH6YycuCkVa3Bc9TWx2gJoZKYqh2q23YEP6L3nTkCqRf0nW
Fy6apiFJzhFmuGGTxNTOLXBOYnUEMLLzPKPcqJBR2mNu09ci+xIk7Lt4lbK7uc+a
HE/OPiXjHH8=
=n9Ef
-END PGP SIGNATURE-


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Win95 Dialin Client Config

1998-02-26 Thread Kevin Traas
Here at work, I've installed a Linux box with a couple of modems hanging off
it for dialin access for remote users.  Everyone can dialin and access the
network, etc.  except that there's one little problem that I haven't been
able to find any docs / info about

None of these dialin users (Win95 or WinNT WS) can browse the network
using Network Neighborhood.  They get a Can't Browse Network message.
However, everything else works fine.  I've got a WINS server running and the
Linux is a DNS server, so name resolution isn't a problem.  However, they
can't use the Network Neighborhood to browse to a server, connect a share,
etc.

Anyone have any ideas on how to get this configured and working?  I'd really
like to get it working because, well, I'm the one with a bit on the line in
suggesting using the Linux box to manage remote dialin users.  Now, people
are starting to ask why we're not using RAS instead?

My thoughts are because it only runs on NT and Microsoft made it...
grin... but the people on my end aren't seeing these as good reasons

TIA,
Kevin Traas


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .