Yeah, the ip address information you would enter when setting up a static ip will very from router to router. I was able to figure out what Jugs446 needed from what he was being assigned on his ethernet adapter. Caterina182, you may need to run that cmd stuff that we talked about earlier in this thread and post your findings to clue us in on what might need to be done.

As for Domain Name Servers (DNS), those are ip addresses of servers that hold the information of what domain name (something.com) equals what IP address (xx.xx.xx.xx). If you didn't have them the only way you could get to a website would be by typing its IP address number.

Jugs446's configuration works fine with him resolving DNS from his router's gateway address. (192.168.1.1), which basically means if his computer needs to know where Daniweb is, it is told via having the dns entered in the connection to ask 192.168.1.1 so it goes and knocks on that door, his router answers, and then goes and asks the dns server that is assigned to it on the wan side, which then goes out and asks all the other dns servers they know of until finally they get the one daniweb is registered to, and it sends them back daniwebs ip address all the way back to his computer so he can then go to it.

Not every router automatically will respond to a dns resolution request sent to its gateway, so you may need to bypass that by entering your isp's DNS servers there instead. You can usually find them by plugging your computer straight in (bypass router) and set to DHCP and autmatically obtain DNS addresses. Do an ipconfig from the command prompt and it should tell you what your isp's DNS servers are.

Also, if you have DSL and your provider uses PPPoE thats a totally different monster. We don't use that here so I've never really worked with it so I can't be of much help if that is the case.