>
> This is something I have been struggling with.
> This is particularly with Win95 dialups.
> If a win95 client dials up to the portmaster using dialup networking PPP
> the remote dialup win95 client doesn't see our local network ie.
> can't resolve DNS addresses locally ( incl virtual domains ). They can
> ping the IP but not
> the Name. We found the only work around is to actually setup TCP/IP protocol
> on the remote clients machine.
DNS is fubar'd? Can their browser get to an IP addy?
My clean it up setup is:
in control panel | network :
1) make sure that Only the Dialup Adapter and TCP/IP is installed
2) disable IPX/SPX, Netbeui, and the clients if not needed. Note:
if you installed this section withOUT the windows client and
netbeui then the vnetbios.vxd isn't normally loaded, meaning
the computer is not vulnerable to a port 139 attack...Just a
lil info..
3) go into properties for TCP/IP
a) ip addressing obtain automajikally
b) disable DNS
c) have NO gateways
d) disable WINS resolution
in my computer | dailup networking | dialling icon :
right mouse click on icon | properties
1) take off use area code country code (we only have local calls)
2) go to server types
a) disable ipx/spx and netbeiu
b) check tcp/ip settings
1) all server assigned and last two boxes checked in
okay out back to dialup networking window, icon still highlighted:
1) go to connections menu | settings
a) click on redial
b) put in 100 (max number) for number of retries
Takes a few moments once you have the pattern down.. 8) and I can talk
almost any user through this in 5 minutes or less...
Note: this is for a setup where we do PAP using RADIUS on Livingston
PM2/3. So the gateway and DNS are passed on...makes life so simple!
-- Aloha,Sherwood