:spam:ing Microsoft !!!
Originally posted by Zoechops
So Luke...
What are YOUR plans for this weekend???

Have you ever been to Baltimore?
So Luke...
What are YOUR plans for this weekend???

Have you ever been to Baltimore?

Seriously though.....if you want to call me, I could probably solve this over the phone. If you want my number PM me.
Show my what to who???
Sure.
I have no idea who team SAKI is,
but, sure!
I'm barely modded: clear corners and side markers, Ricks headrests and waiting on my AEM CAI. Other than that, It's a stock stook.
PM me with more info if you got it. If you'll be attending, I'll show up if for no other reason than to meet a corner brother. Maybe we can get Jimmy to come up from DC (even though I still haven't made it down to see him yet)
Sure.
I have no idea who team SAKI is,
but, sure!
I'm barely modded: clear corners and side markers, Ricks headrests and waiting on my AEM CAI. Other than that, It's a stock stook.
PM me with more info if you got it. If you'll be attending, I'll show up if for no other reason than to meet a corner brother. Maybe we can get Jimmy to come up from DC (even though I still haven't made it down to see him yet)
First, my network is, for now, 2 boxes connected with a x-over Cat5. Previously the server had been 2k and the client XP (for games), but my 2k install was pretty much shot (after about 20 major hardware changes) so I went with XP thinking it would be more efficient (
). The Firewall is software, and the server hands out an IP address based on DHCP. I just remembered that I was forcing the client to take 192.168.0.2 or 3 when 2k was the server. I didn't expect XP's DHCP to hand out IPs scattered throughout the 0-255 range
Also, the client is not sharing anything, only the server (which has a semi-static IP based off my cable modem).
Luke/Joe - Yes, it was the firewall, but when I disabled it before to test things, the client wasn't configured right, so it didn't matter. It acted the same. I should have been persistent in disabling it, but wasn't. Lesson learned.
I may need to change my configuration though. I tried playing an older game that uses DirectPlay, and since the client's IP is 192.168.0.* it doesn't seem to want to play friendly. I can't let the client snag another IP from the cable modem because the fascists at Comcast will charge me. Any thoughts?
). The Firewall is software, and the server hands out an IP address based on DHCP. I just remembered that I was forcing the client to take 192.168.0.2 or 3 when 2k was the server. I didn't expect XP's DHCP to hand out IPs scattered throughout the 0-255 range
Also, the client is not sharing anything, only the server (which has a semi-static IP based off my cable modem).Luke/Joe - Yes, it was the firewall, but when I disabled it before to test things, the client wasn't configured right, so it didn't matter. It acted the same. I should have been persistent in disabling it, but wasn't. Lesson learned.
I may need to change my configuration though. I tried playing an older game that uses DirectPlay, and since the client's IP is 192.168.0.* it doesn't seem to want to play friendly. I can't let the client snag another IP from the cable modem because the fascists at Comcast will charge me. Any thoughts?








that smiley, Zoe!!!)
