• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Two servers walk into a network...

E

Enigma422

Limp Gawd
Joined
Mar 10, 2005
Messages
162
I have a question that I am trying to understand and I'm hoping somebody here can help me out. I have two servers, one is on site the other is in a remote location connected via a private bonded T1. The server on-site and remote are on their own domain and communicate to each other via the T1. Both servers are running Windows Server 2003 Standard

When I am on a workstation I can directly connect to the shared folders on either server by typing \\(Server IP Address) to access the shared folders. However when I am on the servers themselves I have to go to Network Places select the domain before I can see the server on the other domain and access their shared folders. I can ping the servers from each other, but the shared folders cannot be accessed the same way I can access them on the workstations. (Workstations I tested on were running either Win7 or XP).

My question then is, why do I have to take the extra steps on the server to access the shared folders on the other server, where as on the workstation I can access either server the normal \\(Server IP Address) way? I am new to this stuff and am just trying to understand what is happening here. I've worked on home networks before, but this is my first time dealing with business networks.

Thanks for any help/info you can give me.
 
You must log in or register to reply here.
Back
Top