Topic: Unable to browse or send email after wireless A/P change

[Siriosys]

HI,

I'm having a bit of a problem getting my Wireless access point working with SME.  The weird part is that I can ping any external IP and recieve email, but cannot browse at all.  Neither can I send email - I'm assuming this would suggest a DNS issue of some sort, but I'm unsure.

A little background.  My SME box is upstairs a long way from a ADSL phone socket.  I run a wireless-client adapter on the untrusted port of the SME box as the 3COM card works fine with SME.  There is a Dlink G604T Wireless A/P downstairs connected to the net.  All PC's located upstairs are on a wired network via a small switch.

My config is as follows (apologies if this is not worded quite right)

Eth0(Int-192.168.1.254)-Eth1(Ext-10.1.1.254)--Wireless Client adapter-----DlinkG604T(10.1.1.1)-----internet

SME - 7.2
Local PC's are within the 192.168.1.x DHCP range set by the SME DHCP server.

I can ping from both the SME box and local PC's on the network to any external IP.

I changed my wireless router as the antenna had died in the old one and I'm wondering what I might be doing wrong.  Restoring the config is not possible as this is a different version of the router.  A couple of questions:

Should the IP address of the SME box being configured on the Access point's DMZ?
Could Squid be causing my problems with webpages?
Do I need to forward all ports from the Dlink Access point to the SME box?

My apologies for little info, but I'm really in the dark over this.

I've had a search around the forums, but couldn't find any info similar to my setup that I could apply to this situation.


Regards


Rob

[mmccarn]

It sounds as though DNS isn't working.

Try nslookup hp.com from a command prompt on your SME box and see what happens
Then try nslookup hp.com 4.2.2.1 (which will do the same lookup, but try to get the answer from '4.2.2.1', which works from every network I've tried it from in the last 10 years...)

Look at /var/log/tinydns/current to see if you're getting DNS error messages on your SME.

Browsing problems could be caused by the squid proxy, but this wouldn't cause any problems w/ email.

By default, your SME server is trying to do DNS lookups directly from the Internet's Root servers - if your DlinkG604T(10.1.1.1) is blocking or proxying DNS requests this might not work - so if the 'nslookup' tests don't work correctly you might look for a DNS proxy setting in your router.

Lastly, I had the same behavior a few months ago and it turned out to be due to a full hard drive.  Tinydns would fail miserably at every lookup as it tried to update its cache.

  Try df -k and check the 'Use%' on the device mounted on "/".

[Siriosys]

mmccarn,

Thanks for your tips.  I managed to track the problem down........this was a real weird one, but I discovered that the wireless 'client' adapter that I had attached to the server was dodgy.......replaced it with a second identical unit and hey presto!  Up and running and very happy again.

Cheers and thanks for your assistance,



Regards

Rob