Workgroup problems

[Stonehenge]

I have three machines, two running XP HOME and one running OS X Leopard. All are members of the same WORKGROUP. Network setup was run on both XP boxes and are configured with File/Print sharing on. However, when I go to workgroup computers on rig A it doesn't even see itself in a workgroup. The window is blank. Rig B and the mac see each other and are talking fine, but rig A won't talk to anybody.

I have tried turning off all firewalls, but nothing changes.

The XP boxes are utilizing the following in protocols/services:

Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
QoS Packet Scheduler
Microsoft TCP/IP version 6
Internet Protocol (TCP/IP)

I have checked and double checked that the settings are identical between the XP rigs.

Any help would be greatly appreciated, I'm about ready to throw this box of my balcony.

 

[Slowlearner]

First thing to check - is the NIC working? CP>System>device manager>network adapters is there yellow sign on this . If yes reinstall and get latest drivers etc.

Second - is the device getting an IP from the router or does it have a fixed IP consistent with the other PCs on the network

Third - check the router port this pc is connected to - light on? - switch ports and see

Fourth - As a last resort install Netbuei protocol

Let us know waht works

 

[Anubis]

im gonna piggy back on this thread as i have a similar issue,

i have 3 comps running XP pro on the same workgroup, the workgroup is "MSHOME" they all see each other fine and all that, mapped drives all around

i just put together a new comp and its running Vista Ultimate 64 bit, i went into the network settings and set the network to MSHOME however none of the comps can see it nor can it see anything but itself
im pretty sure im just doing something wrong in the settings

Yes its online Yes the nic/router all work im actually posting from it right now

 

[JackMDS]

This can help in checking the configuration of the network components.

http://www.ezlan.net/debug.html

3rd party Firewalls, http://www.ezlan.net/faq.html#trusted

As for Sharing.

Successful Sharing involves some general consideration in Network settings, http://www.ezlan.net/sharing.html

As well as specific adjustment of each computer according to what it is allowed to be shared.

Vista File and Printer Sharing- http://www.microsoft.com/techn...evaluate/vista_fp.mspx

Windows XP File Sharing - http://support.microsoft.com/d...x?scid=kb;en-us;304040

Printer Sharing XP - http://www.microsoft.com/windo...t/honeycutt_july2.mspx

Windows Native Firewall setting for Sharing XP - http://support.microsoft.com/kb/875357

Windows XP patch for Sharing with Vista - http://support.microsoft.com/kb/922120

 

[Anubis]

:lips:

woot i knew i just missed a setting, love how they move them all over the place :/

 

[vexingv]

just anecdotal notes, but sometimes i have trouble accessing computers w/i my network as well (2 winxp pc's, powerbook, winxp laptop) when i try using windows explorer and the network/workgroup tree in the folders pane. many times explorer will time out and report that i don't have access or that the resource is unavailable. however, i've notice that connecting by entering the unc address always works. the syntax is: \\ServerName or \\ipaddress

 

[Stonehenge]

I know the NIC works because I can access the internet from the rig. The ip is consistent and does not match any other rig on the network. I have tried entering the unc address but to no avail. I'm not sure why installing netbeui would be a good idea as it is an "unsupported" protocol and I should be able to do this with nothing more than TCP/IP.

As for the microsoft database articles, I've read thru them and everything appears to be in order.

I still don't understand how this rig could be a member of a workgroup and yet not have itself show up in that workgroup when I got to it's "display workgroup compters" pane.

Still thinking it might go for a flight off the balcony.

 

[Slowlearner]

Right there's your problem - "The ip is consistent and does not match any other rig on the network". The first three sets of numbers must match exactly, only the fourth set can be different - for example 192.168.10.XXX or 10.0.0.XXX (Only 10.XXX and 192.XXx are exclusively reserved for lans) , otherwise there will be no local area network connection. Please report back with what the internal IPs are.

If you can connect to the internet - it means that its not an hardware issue - merely that TCP/IP settings need to be tweaked.

Netbuei protocol eases file sharing within a small network - that it is "unsupported" by Microsoft means nothing - and the two files needed are on the XP cd.

 

[DrGreen2007]

Isnt 172.16.xxx also an available private ip range ?

 

[Slowlearner]

I knew that I get caught very soon - DrG you are absolutely correct

 

[spidey07]

Well to be fair 172.16.0.0 - 172.31.255.255 is the entire range.

As far as not being able to "see" other computers, this is very typical with microsoft browsing. If every single detail is not exactly correct it can be problematic, and even then it can still be flaky. Just use \\computername or \\ipaddress to access and map shares.