Just try to enter your ISP's DNS-Servers in the Properties of TCP/IP (control panel) OR if you are you running your own DNS-Servers just enter your own DNS-Servers You can check your correct DNS-setup when you try to ping your mail-servers on The command-line - if you get any replies your setup must be working... I'm currently running M$ Outlook 2003 and I also tried M$ Outlook Express 6 and M$ Outlook 2000 - both with success Greetings Florian St. > > How do I tell outlook to look up using DNS instead of NetBIOS ... ? > > ----- Original Message ----- > From: "Antony Stone" <Antony@xxxxxxxxxxxxxxxxxxxx> > To: <netfilter@xxxxxxxxxxxxxxxxxxx> > Sent: Wednesday, February 18, 2004 10:05 AM > Subject: Re: Mail Through Firewall > > > > On Wednesday 18 February 2004 1:57 pm, Peter Marshall wrote: > > > > > Hey, I am sure this question is going to seem trivial to > everyone here > .. > > > but I will ask anyway. > > > I want to get outlook to work on my inside box .... I > have it all set up > > > correctly, but it can't find the pop / smtp servers ... > > > > > > I ran ethereal to see what the problem was ... > > > When I try to connect I get 3 requests > > > source 10.0.0.2 > > > dest 10.0.0.255 > > > > That's a broadcast address... > > > > > Protocol NBNS > > > > Ugh. M$ Outlook trying to use NetBios Name Resolution > instead of DNS :( > > > > > source and dest ports: 137 > > > > NetBios.... > > > > > and I get no reply's ... ( well, I get an arp request > after the 3rd try > > > ...) Any ideas how to get this working ? > > > > Tell the client machine (or Outlook, if this is one of > those things which > > Outlook tries to look after by itself, never mind how the > rest of the > machine > > has been configured), to resolve names by DNS, not by using NetBios. > > > > Then it might sensibly look up the IP address of your POP3 > server and send > a > > TCP packet to port 110 on it.... > > > > Regards, > > > > Antony. > > > > -- > > "Note: Windows 98, Windows 98SE and Windows 95 are not > affected by [MS > > Blaster]. However, these products are no longer > supported. Users of > these > > products are strongly encouraged to upgrade to later versions." > > > > (which *are* affected by MS Blaster...) > > > > http://www.microsoft.com/security/security_bulletins/ms03-026.asp > > > > Please > reply to the > list; > > > please don't CC > me. > > > > > >