|
||||||||
Pursuant to internal DNS: it goes without saying! Although, I did notice one little thing: m0n0wall doesn't seem to show preference to the first DNS server listed. I seem to get results from one or the other, all things being equal. Dave -----Original Message----- From: Richard Parvass [mailto:Richard dot Parvass at aaland dot co dot uk] Sent: Tuesday, March 29, 2005 3:33 PM To: m0n0wall at lists dot m0n0 dot ch Cc: David Cavanaugh Subject: RE: [m0n0wall] PPTP server irregularities. For me, having INTERNAL DNS servers specified in the General setup page and un-checking "Allow DNS server list to be overridden..." has it running spot on. Richard -----Original Message----- From: David Cavanaugh [mailto:dcavanaugh at thewebpros dot net] Sent: Thursday, March 24, 2005 9:13 PM To: m0n0wall at lists dot m0n0 dot ch Subject: RE: [m0n0wall] PPTP server irregularities. Oh. Success. LMHOSTS did the trick. Everything the users want works now. Thanks James, et al. Dave -----Original Message----- From: James W. McKeand [mailto:james at mckeand dot biz] Sent: Thursday, March 24, 2005 3:45 PM To: m0n0wall at lists dot m0n0 dot ch Subject: RE: [m0n0wall] PPTP server irregularities. David Cavanaugh wrote: > Thank you the help James. > > However, I found what might be a clue. At the end of Chapter 7 in the > user's guide: "Network Neighborhood in Windows does not work over PPTP > connections because broadcasts are not forwarded across the PPTP > connection" > > Maybe that is why it does not work. Moreover, if it does not work > because broadcasts are not sent over the PPTP interface, is there a > way to enable broadcasts over the PPTP interface? > > And, if it absolutely cannot work, I would like to know, > authoritatively. I will just have to attempt to use RRAS on 2003 for > VPN. You are correct, broadcasts will not work and Windows networking (generally) needs broadcasts to resolve NetBIOS names to IP addresses. Unless you supply your client machine the IP of the server you with to access. This is where hosts/lmhosts or WINS comes in. With hosts/lmhosts you can tell your client machines that <server> is at <IP Address>. WINS does this in a nice automated manner (until the jet database gets corrupt...) Are the remote clients laptops or home computers? If laptops, just add the appropriate lines to the hosts file (or lmhosts if you follow the link in my last post...) next time they are in the office. If the machines are home computers you may need to walk the users threw adding the lines. Home/hotel networks may cause a problem if they use the same subnet as your office LAN. _________________________________ James W. McKeand --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch The information in this e-mail and any files transmitted with it is confidential and may be legally privileged. It is intended solely for the addressee and others authorised to receive it. If you are not the intended recipient, any disclosure, copying, distribution or action taken in reliance on its contents is prohibited and may be unlawful. The opinions expressed in this message are that of the sender and not necessarily those of Aaland Limited. If you have received this e-mail in error please notify postmaster at aaland dot co dot uk |