I am working on a company Intranet page and wanted to hyperlink to some of our internal servers to make it easy to open those locations. On a MAC I can do this using this method "afp://xxx.xx.xx.xxx". But it doesnt work on a PC. Is there a way to do the same thing for a PC? Thanks in advance for any help!
You can just throw the IP address to the webserver into internet explorer and if you have your IIS set up correctly it should bring up your intranet site's default page.
What I am trying to do is link to the IP address of a server in our inside network. Not a website. So in theory a company user would click the link from the Intranet webpage and it would connect you to the specified server inside of our network. Like I said, I can do that on a MAC (OSX) using that afp:// protocol but that doesnt work on a PC.
This is the part that's not entirely making sense. You mean, the browser would load a web page from that server? or are you saying the IE browser would turn into an explorer window and you would be exploring the drives and the directories of the server, or what?
WINS uses a distributed database that is automatically updated with the names of computers currently available and the IP address assigned to each one. DNS is an alternative system for name resolution suitable for network computers with fixed IP addresses. So we're both right depending on the setting
So if the network is running DHCP, DNS would not work due to the IP addresses being dynamic? Its been a while since I did any kind of admin crap so I'm not questioning to be a dick.
Correct, WINS uses a database to keep track of the DHCP addresses as they change... WINS is fine for your smaller networks but isn't as stable as DNS thus the reason most large corporations use static IPs on their machines for DNS. DNS is what is used across the net, URLs are simply a "forwarder" to a DNS server that directs traffic to your server's IP address.
Wouldnt it seem that most large companies (and most of the ones I have worked for have) would want to use DHCP because keeping track of all the static IP's would be a chore?
Doesn't Active Directory use DNS rather than WINS, even machines that are DCHP enabled? I not even close to being an network guy, just wondering.
Protocols are just another way to call a specific port, and sometimes the port is a different one that those common ones on the network. You can... call an Outlook Calendar screen from a webpage: <a href="outlook:calendar">What appointments do I have?</a> Open a server named Blee's share named HeyJude$: <a href="\\blee\heyjude$">open it!</a> start an email Window from a webpage using your computer's default mailer: <a href="mailto:someone@there.com">Send email to someone</a> log in to an FTP server named blah.com with username fu and password bar: <a href="ftp://fu:bar@blah.com">Log Me In!</a> DON'T TRY THIS ONE, though... IE isn't smart enough to erase passwords from the history bar! Finally, you can also invoke Internet Explorer's Help System: <a href="mkMSITStore:C:\WINNT\Help\iexplore.chm::/iegetsrt.htm">Get IE Help</a> (replace C:\WINNT\HELP\iexplore.chm with wherever iexplore's help is) Did you know you could do that? Now you do
I think he must be referring to servers using static ip's, because obviously you wouldn't want to use dhcp there. I've never worked anywhere that used static ip's on the desktops.
As Harrison said I was referring to servers, guess I didn't make that clear now that I read over it... However, keeping tracks of the IP can easily be automated if you your company has the money to do it. I work for a daughter company of the World Bank of Canada (huge, 7000 IT professionals in Toronto) yet my local company only has 300 users. We have our switches assign IP addresses depending on which floor of the building you are on, and they also remember your MAC Address and assign you the same IP everytime you log on... for a static/dhcp kind of hybrid. Your machine is assigned an IP the first time you log on and then it stays that IP even though it is a DCHP setup. Since it is a financial institution we like to have multiple ways of tracking each PC connected to the network at any given time.