Cron wrote:
> Lena Varuolo <(E-Mail Removed)> wrote in message news:<ONnKb.22127$(E-Mail Removed) .com>...
>
>>I have a problem that stumped D-Link's tech support (like that's a big
>>surprise)
>>
>>Recently, I upgrade from dial-up to DSL (verizon). I purchased 2 D-Link
>>DFE-530TX+ NIC's and a D-Link DI-604 Router. I am running my main box
>>with Linux SuSE 8.2 Pro with a dual boot to Windows 98 (Which I hardly
>>use) and have secondary box with SuSE 8.2 Pro only.
>>
>>When I first got the DSL modem and D-link equip, I hooked up the main
>>computer without a hitch, but couldn't network the secondary box. After
>>days of trying, I decided to switch NIC cards to see if I had a faulty
>>NIC. The secondary NIC worked fine on my main box. So I put the NIC's in
>>the original computers, and now my main computer won't display internet
>>pages.
>>
>>I have everything hooked up properly:
>>IP address router: 192.168.0.1
>>
>>
>>IP address main computer: 192.168.0.101
>>Subnet mask main computer: 255.255.255.0
>>gateway: 192.168.0.1
>>
>>I can ping 192.168.0.1 and 127.0.0.1 from my main computer, and I can
>>ping yahoo from my router (through a web-based interface) but I can not
>>pull up a web page through any of my browsers.
>>
>>I shut down my SuSE firewall thinking that it may be blocking my web
>>connection, but I have the same problem.
>>
>>Desperate, I booted up Windows, installed all of the software for the
>>D-Link equipment, configured the network and still the same problem.
>>
>>Then I called D-Link. They couldn't help me. They did say my router and
>>NIC were working fine, so my computer must be the problem.
>>
>>Any suggestions? I am currently using a friend's dial up connection and
>>really miss my DSL.
>>
>>Thanks in advance for any assistance.
>>
>>~LenaG
>
>
> Sounds like DNS problems.
> Have you tried resetting the router to factory default, then
> re-entering all of the IP data? I had to do that with mine because it
> cached the wrong DNS IPs and wouldn't dynamically update them.
Thanks Cron and Johnny Bobby Bee! You were right, it was a DNS problem.
I am a just venturing into networking and had idea where to look!
Everything is working fine now.
~Lena
|