I have a D-Link DI-624 router, a laptop running Windows XP SP2 and using an integrated wireless connection, and a desktop running Win2K server with a USB wireless adapter. Since I will be doing port forwarding to these computers, I plan to assign the two computers static IPs. My current configuration is the following: Laptop (wireless) ---------------- IP 192.168.0.100 Subnet 255.255.255.0 Gateway 192.168.0.1 DNS 192.168.0.1 Desktop (wireless) ---------------- IP 192.168.0.110 Subnet 255.255.255.0 Gateway 192.168.0.1 DNS 192.168.0.1 My Internet connection is fine on the laptop, as I can access websites without a problem. With the desktop, however, I cannot. On the desktop, the USB Adapter's Management Console indicates that I am connecting without a problem to the router, yet I cannot access websites or even ping 192.168.0.1 from it. What am I doing wrong? Also, on occasion I plan to plug both computers directly into the router for wired connections. When I tried to give the disabled wired connection on the Windows 2000 server a static IP of 192.168.0.111 in anticipation of those times, it gave me a warning about multiple gateways. It is not currently set that way now, but, once I get the other stuff figured out, is it OK to add this information? Any help would be appreciated.

Try setting them up for dynamic IP addressing, but create reservations within the DHCP server setup of the router. "If that [soiled bed] sheet is a [holy] manifestation, then I'm working on a miracle in my Jockey's!"

Are you running any encryption on the router? If so, are you sure that you have applied the key properly to the USB Adapter on the desktop? I only ask because a friend of mine had a similar problem with D-Link products. His wireless router is a Linksys, but he had a PCMCIA D-Link adapter. He is running 128-bit wep on the router. When he configured the PCMCIA adpater with the wep key, he entered the "pass-phrase" instead of the actual hexadecimal key. Although this was incorrect, his D-Link Wireless utility reported that he was indeed connected to the WLAN. When I had him run an ipconfig to see if he received an IP from the DHCP server, we found out he didn't, so that is what tipped me off to double checking his WEP configs.

WEP doesn't use a "standard" algorithm to generate encryption keys from passcodes so if your router and adapter aren't by the same company they probably can't share passcodes: You have to manually input the router's hexdecimal encryption key into the adapter, yes. I don't think WPA encryption suffers from this shortcoming. Make sure your firewall allows access to the IP addresses you've chosen and these are entered correctly into port-forwarding. If you have a software firewall on the client either disable it or tell it that IP range 192.168.0.1 through 192.168.255.255 is "local" or "trusted".

SmittyZ3M, that did the trick. Thanks so much for the help, everybody.