On Thu, 2003-01-30 at 09:22, Levinshtein, Eyal wrote: > > I have a crazy problem with Redhat Linux 8.0 (psyche) > > I have a Toshiba Tecra 8000 laptop PII, 400mhz, 128mb of Ram. > > ---- > Background info: > > I have Windows XP installed and running with Wireless networking configured > and working. > > In Windows XP: > > >ipconfig /all > > Physical Address. . . . . . . . . : 00-02-2D-08-15-AB > Dhcp Enabled. . . . . . . . . . . : No > IP Address. . . . . . . . . . . . : 169.254.93.100 > Subnet Mask . . . . . . . . . . . : 255.255.0.0 > Default Gateway . . . . . . . . . : 192.168.1.1 > DNS Servers . . . . . . . . . . . : 167.206.3.207 > 167.206.7.4 > > The Access Point (Lucent AP-500) is connected to a (Linksys router > BEFSR411). The access point is configured to obtain IP > automatically. On Windows, I had to specify the DNS and Gateway > settings in order for the laptop to get connected. (Anyone has any idea > why the Lucent AP was not able to set DNS and Gateway? -- or am I missing > something -- That was in windows) > > ----- > In Linux > > I installed Red Hat Linux 8.0 2.4.18-14 on the same laptop and attempted to > apply the same configuration (same IP, same DNS, same Gateway as I had > setup on Windows.) But It does not want to work. > > Everything seem to be working, the card is active, but I am unable to ping > (192.168.1.1 -- The Linksys Router, and what suppose to be the gateway), I > am unable to ping (169.254.93.1 - The Lucent Access point ), and I am > unable to ping the DNS servers. > > What am I doing wrong? Bellow are some information that may be helpful > to you. Your help is extremely appreciated. I went through all the > HOW-To and went to tons of web sites that offer help, I hit a wall, I do > not know what to do. > > Eyal Well, for starters, you're not even on the same IP network as your router. With a gateway of 192.168.1.1 and a subnet mask of 255.255.0.0, your IP address MUST be 192.168.x.x, where the x's are any number between 1 and 254. However, I would go so far as to recommend you change your subnet mask to 255.255.255.0, and use an IP address of 192.168.1.x. Assuming that the driver modules are loading correctly (and it looks like they are), and that your wireless config (ad-hoc, channel, etc.) are correct, this should fix your problem. -- Dave Sherman MCSE, MCSA, CCNA "If we wanted you to understand it, we wouldn't call it code."
Attachment:
signature.asc
Description: This is a digitally signed message part
