dataDude
04-18-2004, 04:58 AM
Ok, first time doing one of these threads, seeing who can give the right answer(s).
First, I have an infrastructured wireless network set up at my desk for only 2 computers (for now. I will be adding another computer as a dedicated server later), the DHCP being a router that can also connect through 10/100BaseT, and includes Ethernet Internet capabilities. I'm new at this stuff, but I understand the basics. At times, both computers will see the DHCP and will be given IPs for each, sometimes one won't always get an IP from the DHCP but the other computer will see it anyway. Sometimes only one computer will see it and sometimes neither one. It's all so frustrating and unpredictable. Sometimes all I need to do is restart the router and that will do it, but the network will only hold for (the record) a half hour. If ever I get the WINS autoconfig for the IP and I try the /renew param, 99% of the time it won't work and tells it can't see the DHCP. That's the majority of the time. Now, the only way I was able to get the two to see each other for the first time was when I wired it all together. Strange. Also, when my network is going I have to stay disconnected from the Internet or else it overrides my network and the network shuts down. I have DSL Internet, but I can connect through 10/100BaseT, but the router doesn't want to see it. Therefore, I can only connect through a direct physical line to the computer. My plan was to connect the DSL to the router and then wirelessly connect that to the computers, but so many things have failed that that's only a dream to be fulfilled right now.
Note: the router seems to be fine because a co-worker tried it at his place and it worked fine for him. I can also ping the localhost just fine. At times when I have the IP address from the DHCP I can't always ping the computer's own IP, but the other will. I hate this.
First, I have an infrastructured wireless network set up at my desk for only 2 computers (for now. I will be adding another computer as a dedicated server later), the DHCP being a router that can also connect through 10/100BaseT, and includes Ethernet Internet capabilities. I'm new at this stuff, but I understand the basics. At times, both computers will see the DHCP and will be given IPs for each, sometimes one won't always get an IP from the DHCP but the other computer will see it anyway. Sometimes only one computer will see it and sometimes neither one. It's all so frustrating and unpredictable. Sometimes all I need to do is restart the router and that will do it, but the network will only hold for (the record) a half hour. If ever I get the WINS autoconfig for the IP and I try the /renew param, 99% of the time it won't work and tells it can't see the DHCP. That's the majority of the time. Now, the only way I was able to get the two to see each other for the first time was when I wired it all together. Strange. Also, when my network is going I have to stay disconnected from the Internet or else it overrides my network and the network shuts down. I have DSL Internet, but I can connect through 10/100BaseT, but the router doesn't want to see it. Therefore, I can only connect through a direct physical line to the computer. My plan was to connect the DSL to the router and then wirelessly connect that to the computers, but so many things have failed that that's only a dream to be fulfilled right now.
Note: the router seems to be fine because a co-worker tried it at his place and it worked fine for him. I can also ping the localhost just fine. At times when I have the IP address from the DHCP I can't always ping the computer's own IP, but the other will. I hate this.