SMC Barricade - PC Sharing Problems

[tekweeny]

I have two PC's (running Win2kPro) (A) and (B) hooked up to my Barricade and both are surfing like bandits. However, I can't get (B) to ping (A) - results in a "request time out" (I can, however, get (A) to ping (B).
Therefore, since I can't get them to ping in both directions I obviously won't be able to get them to share files and other devices. Here are the specifics between (A) and (B):

(B)
- is my own personal PC and is set up to
obtain an IP Address dynamically (DHCP)
- set up as a "WORKGROUP" PC.
- Protocols a) MS Client (blah, blah...)
b) Printer and File Sharing
c) TCP/IP

(A)
- is my company's PC and it is set up as
DHCP as well.
- set up as a domain PC (my company's NT
Domain)
- Protocols ...) same (B)

So my ISP is really my company's domain/firewall. But like I said I can't get (B) to ping (A), whereas (A) pings (B) just fine. Does anybody have any ideas how I can get these PC to share files and resources (eventually, is it possible to share the CD-ROM/CD-RW on (B) with (A))? I don't know the specifics of how to configure Win2kPro or the Barricade itself for networking so it might have something to do with those two things on top of the fact that (A), my company's PC is configured to the company domain and (B) is on it's own workgroup.

Any information would be greatly appreciated.

Thanks!

 

[fargus]

I'd say it's most likely the domain name... your work PC doesn't have a trust relationship with your personal machine, since it is in a different workgroup. You could try changing the workgroup name on the personal machine to be the same as the company domain, but if you're connected to the company it may start showing up in their logs which could generate some unwanted questions from the sysadmin...

 

[tekweeny]

Actually PC (A) is configured as a "Member of Domain" and (B) is configured as a "Member of Workgroup". So do you think that I am basically SOL?

 

[tekweeny]

OK, I finally got (B) to ping (A). I'm running Zone Alarm on (A) and when I shut it down (before pinging) it didn't shut down all the way as I noticed an orphaned process in the task list. Once I killed it (B) was able to ping (A) just fine.
Now, both PC's can ping eachother via IP address just fine. However, (A) can ping (B)'s host name but when (B) pings (A)'s it times out on top of the fact that it displays a different IP address for (A) than my router assigned via DHCP. I'm assuming that the IP that showed up is the one that is assigned to my PC on my company's Domain. I'm not sure what the problem is because (B) is sharing it's printer and drives/files with (A) and (A) is sharing it's drives/files with (B) as well.

Any ideas?