Wireless woes

Reply Subscribe

Thread Tools

Search this Thread

Sep 6, 2004 | 07:31 AM

#21

MvCrash

Contributing Member

Joined: Jul 2004

Posts: 342

Likes: 0

From: Northern NJ

Quote:

Originally Posted by amusement

MvCrash I think nailed the possibly cause of the problem. If the bridge was offering an IP address starting with 169.x.x.x (default Microsoft) and the client was either static or wasn't asking for a new IP address then fubar indeed.

Wireless host ot host: ADHOC

I perfer using cross over cables and adding static IP address with each client having the other client's IP address has a gateway.

I used this setup to backup files between a host and a server both on a wireless network. Something about 100 meg network interface versus 11 meg wireless that motivated me.

Greetings,
Most non-routable addresses default to 192.168.xxx.xxx for an Ip address. Cross over cables are used to connect like devices ie: router to router, switch to switch or PC to PC.
If your IP software in configured properly, then you should be able to mix static and dynamic IP addresses as long as they are on the same subnet and contain the same mask ie: 192.168.xx.xxx. 255.255.xxx.xxx (B Class non-routable subnet)

Sep 6, 2004 | 07:43 AM

#22

MvCrash

Contributing Member

Joined: Jul 2004

Posts: 342

Likes: 0

From: Northern NJ

Quote:

Originally Posted by CynicX

explain to me what this is actually doing and how it can help a connection....I like knowing what is actually happening when I do stuff...thanks

Cynic,
Churned indicated that he was having trouble getting the wireless device to work. Then he stated it started working and that he thought the network addressing was screwed up but he really did'nt know what he did.

This works with Dynamic Addressing in which a server or ISP provides you with an IP address through the network or a router that assigned IP addreses using DHCP.

If you have a wireless device that goes from one network to another and you have trouble getting your PC to drop old net settings and picking up new ones most times you have to reboot. If you don 't completly power off the PC or laptop the settings may persist and cause alot of headaches.
If you find yourself in some type or trouble with network settings, going to the command prompt click start>run and typing "ipconfig /release" will flush all the old settings of the IP Configuration. The in order to force the PC to contact whatever device is running the dynamic IP software you then type "IPCONFIg /renew". After, you can view the IP configuration settings by typing "IPCONFIG /ALL". You ned the "/All" or you won't see the DNS and dubnet settings or if you have more than one adapter, all adapters.

Hope this helps.

Sep 6, 2004 | 07:44 AM

#23

amusement

Registered User

Joined: Nov 2003

Posts: 1,537

Likes: 0

From: Portland, Oregon

In deed!

FYI: IP address are routable just 192.168.x.x or 10.0.0.0 and finally 172.16.0.0 aren't routed throught the internet.

But, doesn't invalidate your point. You are correct sir!

Sep 6, 2004 | 07:54 AM

#24

MvCrash

Contributing Member

Joined: Jul 2004

Posts: 342

Likes: 0

From: Northern NJ

to be exact:

Non-Routable (Private) IP Addresses
We recommend non-routable IP for home networks. These IP addresses have been set aside for use in home and office networks, when it isn't necessary (or even desirable) to use a public IP address. They are especially useful to the DSL user who has multiple computers connected to a single proxy server, firewall or router (see our Network Overview for details).

Reserved IP addresses for private networks
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255