:spam:ing Microsoft !!!
Registered User
Joined: Sep 2002
Posts: 10,342
Likes: 0
XP's firewall is off. Actually, I wonder if I turned the browsing service off (or didn't turn it on), which would explain why the server can't see itself. I'll try the traditional mapping procedure when I get home Luke, I didn't think of it last night.
Computer names are Deli and Games, workgroup is WSDeli - nothing that should cause a problem.
Computer names are Deli and Games, workgroup is WSDeli - nothing that should cause a problem.
Have you tried pinging the computers to each other?
Go to 'start' , 'run' and enter 'cmd'. When the Dos window comes up, enter 'ip config' that should give you the ip address of the computer. Go to the other computer and go into the dos window and enter 'pingxxx.xxx.x.x (ip address of other computer) and hit 'enter'
If the procedure times out, then I don't think the computers are even able to talk to each other yet. I'm having a problem with my 3 XP machines, but I haven't really dug all the way into it yet. I have used a cross-over cable and the servershared method that Luke mentioned, but I haven't been able to use it with the router yet.
* edited to include a previously ignoredCORNERR - OOOOSKY!!!
Joined: May 2001
Posts: 93,305
Likes: 820
From: Nowhere
Day late Zoe 
I've heeded Luke's advice and circumvented the windows workgroup crap. That part still isn't working right, however, I have functioning communication between the computers now. I think my main sticking point is that XP assigns IPs differently than 2k did. When 2k was on the server, the client always got an IP of either 192.168.0.2 or 192.168.0.3, the first available IPs after the gateway's IP. So my firewall was setup to permit 192.168.0.2 through 192.168.0.9. Well, after putzing around, I realized XP was handing out high IPs to the client - 192.168.0.68, 192.168.0.134, and 192.168.0.97 on different reboots. Once I opened up the firewall's IP restriction, I could at least ping both ways. I changed the username and (added a) password on the client to match the server, and that allowed me to map the drives.
Now I just gotta figure out DirectPlay...
I've heeded Luke's advice and circumvented the windows workgroup crap. That part still isn't working right, however, I have functioning communication between the computers now. I think my main sticking point is that XP assigns IPs differently than 2k did. When 2k was on the server, the client always got an IP of either 192.168.0.2 or 192.168.0.3, the first available IPs after the gateway's IP. So my firewall was setup to permit 192.168.0.2 through 192.168.0.9. Well, after putzing around, I realized XP was handing out high IPs to the client - 192.168.0.68, 192.168.0.134, and 192.168.0.97 on different reboots. Once I opened up the firewall's IP restriction, I could at least ping both ways. I changed the username and (added a) password on the client to match the server, and that allowed me to map the drives.
Now I just gotta figure out DirectPlay...
Registered User
Joined: Sep 2002
Posts: 10,342
Likes: 0
That's funny, mine was assigning 192.168.0.3 and 192.168.0.4, but still no dice. Mine aren't pinging either. I'm gonna get with my buddy who works for Microsoft this weekend. He IS God as far as I can tell.
Joined: Jun 2002
Posts: 42,315
Likes: 45
From: Central Massachusetts
Ah shit, I missed mom's spaghetti last night. 
Billy, glad it's sorted out. Interesting. So XP is handing out different IPs than W2K? I'll have to look into that. I've never configured a Windows machine as a DHCP server.
So, it was your firewall after all (rejecting the new IP range)... I thought you'd said you'd disabled that during your testing.
DHCP address assignment can be a bit of a pain. Static IPs really help for machines that are exporting shares etc...
Best wishes.
Billy, glad it's sorted out. Interesting. So XP is handing out different IPs than W2K? I'll have to look into that. I've never configured a Windows machine as a DHCP server.
So, it was your firewall after all (rejecting the new IP range)... I thought you'd said you'd disabled that during your testing.
DHCP address assignment can be a bit of a pain. Static IPs really help for machines that are exporting shares etc...
Best wishes.
Joined: Jun 2002
Posts: 111,882
Likes: 2,034
From: SoCal
Originally posted by wicky
as I am Really nervous about shootin photos of him today now I will just picture him in this pic and I will be fine!!!
Maybe I should print it out and take it with
Registered User
Joined: Jun 2001
Posts: 18,759
Likes: 0
From: Wheeler Army Airfield, HI
Originally posted by WestSideBilly
ing firewall!
I changed a couple settings from my 2k box, and now that I have the client set up right, it's working.
Thanks for the help guys.
ing firewall!I changed a couple settings from my 2k box, and now that I have the client set up right, it's working.
Thanks for the help guys.
So it was the firewall? Glad that you found it.