• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

why is windows networking so stupid ?

WeiWei

Member
hi guys,

This is a " seek for help" and complain message about windows networking.

My friends in my house share a broadband connection using a D-Link router. There are 8 computers in my house and all of them can connect to the internet.

The problem is when we are setting up a network using windows networking.

6 of these computers can be connected to the network successfully, sharing files and all. The other 2 don't seem to be able to connect to the same network although it is set up the same way with the same workgroup name.
The other computers can see the 2 problem comps, but can't access its files. The problem comps can't see a thing.

Another question is why does windows always want to set up a bridge when I let it automatically configure ? Can't that darn "Bill Gates money making thing" know that I am already sharing a connection ? It seems to me Windows can't handle router shared connections.

Anybody have a way for me to solve this problem ?
 
Originally posted by: WeiWei
Why is windows networking so stupid ?
Look at this as a Positive thing here is your chance to write a better OS and become rich and famous.

Or may be you just need to read carefully and slowly the instructions.

Log to this page it has a lot of links to instructions to Windows Network Setting and Sharing.

Link: Installing & Sharing

 
Having essentially no useful information except that the network doesn't work, it's hard to suggest a course of action.
rolleye.gif
 
Definitely give us more information, and do so after reading through the FAQs JackMDS posted.

You said the 2 "problem PCs" are set up the same way - which version of windows are they? Are there any antivirus software installed on them? Look through the networking FAQs - maybe just installing NETBeui will do the trick
 
heh,sorry guys for not giving more info.

the 2 problem comps are running on XP Home Edition and the common thing about the 2 is that they are newly bought, if that has any significance. One was bought from DELL and one from Compaq with their respective OEM XP Home.

There are 3 other users on my network who are using XP Home as well, but they aren't new, they had them for quite some time. They didn't have a glitch when setting up into the network.

I sorta solved the problem by changing to XP Pro, and everything went smooth... didn't have to do a thing !!

Could it be that new OEM versions of XP Home have something missing ?

Thanks for the replies..
 
I suspect it was just a configuration issue. One thing is that NETBIOS over TCP/IP may have been disabled, but since the evidence has been erased, we'll never know. 😀
 
Well, actually, there's still one computer which I didn't "convert" to XP Pro. So the evidence is still there..

Netbios over TCP/IP... do I need that for windows networking ? I don't have it, and I don't think any user on my network has it either..

Anyway, gunrunnerjohn, what is the solution you suggest ?
 
I suggest you open a command prompt on the non-working machine, and type:

IPCONFIG /ALL

Post the results, and we'll see if we can get your computers talking. 🙂
 
Ok, here's the info I got on screen :

Windows IP Configuration

Host Name : <some name>
Primary Dns Suffix :
Node Type : Hybrid
IP Routing Enabled : No
WINS Proxy Enabled : No

Ethernet adapter Local Area Connection :

Connection-specific DNS Suffix : up.chartermi.net
Description : Broadcom 440x 10/100 Integrated Controller
Physical Address : 00-0B-DB-B9-32-47
Dhcp Enabled : Yes
Autoconfiguration Enabled : Yes
IP Address : 192.168.0.102
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.0.1
DHCP Server : 192.168.0.1
DNS Servers : 192.168.0.1
Lease Obtained : <some date>
Lease Expires : <some date>

Thats all I got... hope it helps..
 
ok, do i have to install netbios in all the other comps for it to work ?

I've installed it in the problem comp and it didn't help.

There has to be an easier way out of this... damn XP Home....
 
Back
Top