Need to forward DNS requests from Linksys FW : Linksys, WRT54GS

May 17, 2008 09:28am pdt

1. batry_boy 225,050
2. lrmoore 72,675
3. dpk_wal 45,375
4. Cyclops3590 32,326
5. MrHusy 30,000
6. RobWill 25,325
7. from_exp 24,385
8. rsivanandan 22,700
9. stuknhawaii 21,000
10. naughton 18,880
11. mkielar 17,700
12. harbor235 15,248
13. arnold 14,876
14. mwecompu... 14,105
15. ccomley 12,692

1. lrmoore 1,028,547
2. batry_boy 416,279
3. RobWill 348,824
4. rsivanandan 223,719
5. grblades 117,615
6. dpk_wal 108,375
7. JFrederi... 99,519
8. pseudocyber 90,643
9. harbor235 88,364
10. nodisco 79,022
11. Cyclops3590 77,354
12. calvinetter 76,413
13. PeteLong 70,931
14. Joesmail 65,623
15. Freya28 65,550

04.30.2008 at 07:09PM PDT, ID: 23367472

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

Need to forward DNS requests from Linksys FW

Zones: Networking Hardware Firewalls, Miscellaneous Networking, Windows Networking

Tags: Linksys, WRT54GS

Hi Experts. I have a Linksys wireless router (WRT54GS) that is connected to TimeWarner's T1 router. I need to forward DNS requests from my client's pcs to TW's router. How do I create this rule on the Linksys FW?

Start your free trial to view this solution

Question Stats

Zone: Computer Hardware

Question Asked By: samiam41

Solution Provided By: Netman66

Participating Experts: 1

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

04.30.2008 at 07:34PM PDT, ID: 21476192

Rank: Master

Netman66:

If the clients get addresses from the Linksys, then there is nothing to do. Generally it uses the ISP's DNS server addresses (or it's own IP address) to give to the client. It will proxy DNS requests for the internet.

Unless you've changed any default rules, then DNS is port 53 and should be allowed outbound.

04.30.2008 at 07:39PM PDT, ID: 21476221

samiam41:

The clients are using the domain controller as the dns server and the forwarders are set on the server. The traffic is just moving so slow and I have narrowed it down the fw.

How would the entry read for the linksys device?
App Name >> Start / End >> Protocol >> IP Addr
DNS 53 / 53 Both Server IP?

04.30.2008 at 07:48PM PDT, ID: 21476255

Rank: Master

Netman66:

Ok, here's what to do.

Turn off DHCP on the wireless device - clients should get DHCP from the server. The WAN port is connected to the ISP router and the server (or LAN switch) to one of the switch ports on the router.
Make sure your DHCP scope on the server is the correct network - example: the router address is 192.168.1.1 then your scope should be 192.168.1.1 - 192.168.1.254. Add an EXCLUSION for the router and the server's IP.
Point all clients to the server for DNS (done in the scope or server options).
Point your server to itself for DNS (done on the NIC on the server). NO ISP ENTRIES HERE!
Set a Forwarder in DNS to the ISP (done on the properties of DNS server).
Uncheck the box in the router for DNSmasq and any other DNS options to use the ISP DNS (done on the router's web interface).

There should be no need to configure apps or rules for DNS at all. If your clients are slow there is a basic configuration problem somewhere.

04.30.2008 at 07:49PM PDT, ID: 21476264

Rank: Master

Netman66:

Another issue I have discovered with Linksys is that some Firmware versions are dead slow. What version are you running on that? I had to flash back to an older firmware on a wired router I had here to bring back fast connections.

04.30.2008 at 08:03PM PDT, ID: 21476292

samiam41:

Great information. From your first of the last two posts, I see one thing I have configured differently. I am using 192.168.1.200-210 for the DHCP scope even though the server and fw are 192.168.1.1 and .2. Could that throw it off that much? I think I have something similar at home.

Oh yeah and I don't remember unchecking the box for DNSmasq. I will check into that next.

I hate how stupid easy this will be once the issue is found. That is the part that is p!ssing me off. I know there is something basic and I am looking past it. I sure hope you nail this so I can stop thinking about this issue.

As for the last post you did, the version is 1.52.2

Thanks again for your help.

04.30.2008 at 08:12PM PDT, ID: 21476311

Rank: Master

Netman66:

No. The scope is generally the entire subnet, but as long as the Subnet Mask, Gateway and DNS is given out correctly then it's fine.

Flip over the router and find out the version number for me please!

Is DHCP being served from the server or the router?
If it's on the server now, did you turn the DHCP service off on the router?
You are making sure that the DHCP options are set to 003 - router, 005 and 006 your server only?

04.30.2008 at 08:17PM PDT, ID: 21476321

samiam41:

I would love to flip the router over but I am remoting into the client's office so I can't see the device. I believe the version is 5.

The AD server is now the DHCP server and the DHCP service on the fw is off. I did not configure WINS, only DNS and gateway.

04.30.2008 at 08:26PM PDT, ID: 21476343

Rank: Master

Netman66:

LOL!

Sorry, I thought you were onsite! The latest version is 1.52.5. I'd flash it onsite next opportunity.

Your want the server to be DHCP - good. Scope is 192.168.1.x-.254. Exclude .1 and .2. Subnet mask should be the default class C - 255.255.255.0. Gateway is the router (.1, I presume) and DNS is .2 ONLY!
Make sure to set option 005 AND 006 for DNS.

Remove any rules for DNS from the router. It may interfere.
Forwarder on DNS should be the ISP's DNS server IPs.

Reboot the client PCs to refresh their IP stack.

Let me know.

Accepted Solution

04.30.2008 at 08:35PM PDT, ID: 21476370

samiam41:

: )

As for the firmware, will do. I am rebooting the pc's now and will let you know what i find. I typically right click on the network connection and choose repair to flush out all the old crap and then reboot. I hope that didn't throw a wrench into what you wanted me to test.

04.30.2008 at 08:42PM PDT, ID: 21476396

Rank: Master

Netman66:

No it's fine.

You should be able to run a Tracert from a PC to somewhere out on the internet and see where it goes. If any of these are Vista then a pathping may also show the route.

04.30.2008 at 08:53PM PDT, ID: 21476423

samiam41:

Ok. I restarted the computer and I think I can tell some difference. Not a major difference but I think the remote connection to their server and then using VNC into one of their computers impairs that assessment for me. I just sent them an email to try out the internet in the morning and let me know what they find.

I am heading to bed. Enough fun for one night. Thank you again for all of your help and insight. There are several people here grateful for your time. Take care and I will update this ticket in the morning.

04.30.2008 at 08:54PM PDT, ID: 21476424

Rank: Master

Netman66:

Have a good one. I'm off to bed also - 1am here!

Talk in the AM.

NM

05.01.2008 at 09:58AM PDT, ID: 21480410

samiam41:

Well, here is the update. I asked the client to contact TW and have them check their system out further. The belief now is that there is a problem with the Linksys device. Not sure I come to the same conclusion but the network is still slow this morning and the client is going crazy. Whatever they want to try out. They are going to buy a new Linksys device and have TW configure it.

Once that fails, I will let you know. Thanks again for your help. I can't believe we went through all that until 1am yesterday.

05.01.2008 at 10:11AM PDT, ID: 21480539

Rank: Master

Netman66:

Once that fails..... LOL - too funny!

It's possible it's a firmware issue - you should suggest they flash it first before wasting time buying and installing a new one.

05.01.2008 at 10:13AM PDT, ID: 21480557

Rank: Master

Netman66:

It could also be a demark problem with the T1. Have they attempted to reset the T1 circuit/endpoints?

05.01.2008 at 10:19AM PDT, ID: 21480614

samiam41:

: ) Sad but true.

I will recommend they do this. I have a feeling they are going to take a harder pounding financially by going this route. I tried to talk them out of it but the company is all women and they made their mind up.

05.01.2008 at 10:21AM PDT, ID: 21480637

samiam41:

I don't think they did. TW was so focused on finding something on someone else's end that I think they may have jumped a few steps. TW has a bad history with that building and knocked out the internet access for several of the business for 2 weeks earlier this year. I think they are looking for something else to be problem. That is a really good recommendation though and one that I posed two weeks ago when I first started working on this issue.

05.06.2008 at 10:58AM PDT, ID: 21509469

samiam41:

Well, here is the answer. I called them yesterday morning to find out how their test went and much to my surprise, it didn't work. Looking back through everything, the only thing left to switch out was the cisco switch. That ended up being the problem. SOB! So the switch was replaced and I can finally go on without having them call me every day.

Thanks to everyone for your help. I am sure that through that entire freaking process, I fixed several other problems that would have shown up as soon as I replaced that switch. Your suggestions and technical knowledge saved me from creating 3 more EE tickets. I am working on the points now.

05.06.2008 at 10:58AM PDT, ID: 21509474

samiam41:

Netman66, I think you owned this one.

Netman66

05.06.2008 at 12:23PM PDT, ID: 21510161

Good to hear. Perhaps now you'll have some peace!

20080236-EE-VQP-29 / EE_QW_2_20070628