|
,Currently both were set to get their own address. Which neither seemed to do that. I put in ip address for them both with no luck in getting them to talk.
However, I do have the services ready to post in case there is something wrong there. I have a window's default and a tweaked for profiles.
One thing I found last night when I was goofing around was this. It was under the Microsoft .NET Framework 1.1 wizard. I'm not sure if it's worth mentioning but I will.
The wizard brought a window similar to setting up your internet blocks and access for websites. It is set to just under full trust access. And it said in full detail: Programs might not be able to access most protected resources such as the registry or security policy settings, or access your local file system without user interaction. Programs will be able to connect back to their site of origin, resolve domain names, and use all windowing resources.
However, I didn't mess with this setting yet.
After doing some more poking around and trying to set the ip address manually again, and being in my tweaked profile. I opened up to see if I could see the computers on the network. I'll be damned if I could see hers and mine on hers.
But on mine, I got this message: Mshome is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission. The list of servers for this workgroup is currently not avaible.
Hmmm... looks like it's just a issue on my computer to fix?
|