problem with XP pro peer to peer network

kanezfan

I have this client, he's got three identical dell PCs that are all windows xp pro. I ran windows update on all of them, they're all patched as of yesterday, SP1 included. They all have the same identical network settings, get their IP address through DHCP from the DSL modem, and all belong to the same workgroup. Of course, they all have different machine names. Machine A has a shared printer. Machine B and C are just going to be used for email and printing to machine A. So can someone please explain why it is that when using machines B, I cannot access Machine A unless Machine C is either not part of the workgroup, or shut off? Furthermore, when trying to use shares on Machine C from Machine B, I'm getting prompted for a password for the guest account. I didn't turn on the guest account on Machine C, and I didn't change the guest account password either. There is also a windows 2000 server in the workgroup, but it does not do any domain authentication. It is a standalone machine, only to be used for storage (4 SCSI drives in one 160GB aray) I hate when you get these types of problems, they make absolutely no sense at all. I'm on the verge of formating all three PCs and starting over. btw, I didn't set up the machines, this guy called me and told me he'd tried to network them himself but couldn't do it. I got them all online, but this is really annoying.

They are all on the same windows peer to peer network, same workgroup name, so what is the problem?

shwaip

he may be limited to a certain number of IPs from the dsl company, 3 is a common number. Once you have the fourth pc on the network, you may hit some problems.

kanezfan

nah it's not that. the thing is, they all have IP adresses, it's just that when machine C is alive, you get an access denied error when trying to browse the shares on machine A from machine B.

Tex

How are they all three getting ips from the DSL modem? is it lugged into a router or switch or does one of the pc's provide ics sharing? Usualy you connect a modem to a single pc and it shares its internet connection with others in the network unless they are using a router. You want each one to be protected and firewalled and its harder having them all open to the net. Stick a second cheap nic in one computer and let it get its IP from the dsl modem. Then set the other IP on the nic thats connects that box to the network to 192.168.0.1. Let the other computers still get their IPS thru dhcp but now the pc sharing its connection assigns the IPS and protects them thru its firewall. Just run teh network setup wizard on all three after you get the one sharing the internet up. And.. make sure every user has a password and is is entered onto EVERY PC. All three pc's want all three users.

Tex

QCH

I had the same problem last year when I first got my Cable modem. I had three systems all hooked into a 4 port switch that went to the cable modem. The problem is that my provider only allows a predetermined hardware addresses and each PC gets a different IP address and may even have different IP range.

I decided not to setup a PC to "share" the connection. I put together a PII 400MHz Linux Firewall that acts as a firewall (duh) and a DHCP server. Cheap and works great. The firewall keeps almost all of the "bad guys" away and allows me to plug any number of PC's to my network and not have to contact my ISP and have them reset the hardware address database.

My 2 cents...

Straight_Man

Right, either a router that gives DHCP and masqs as one box or a dedicated BSD or Linux pseudo-router is better than an ISP-visible P2P network. Comcast limits total bandwidth shared to modem also, and by trying to use the modem for throughput and modem DHCP you also run into modem DHCP IP range and number limits. Violates get either an out-of-subnet IP or no DHCP and use default IP. Any modem that is remote maintainable can get limits fo number and subnet range fed into it by ISP at any time they want, they are typically remote managable modems.

The Netgear RP614 can be used with high-speed DSL and Cable, can feed DHCP, and can have SNMP shut off and most ISP mgmt ports as well as about 95% of all UDP ports and any non-standard TCP ports shut off at router from a browser run from either of the two boxes I normally have hooked to it. I do not violate bandwidth rate caps, so my ISP does not care.

John.

kanezfan

it might be a switch, I'm not sure, but all the PCs are connected to the switch/router, and the modem is connected to the switch/router. the modem handles the pppoe connection, which isn't the problem. the problem is that it's a windwos workgroup and the PCs don't work correctly with each other.