You want to first understand why the log grew to that size - Do you know why? Are you using CDC, replication, have a long running transaction or any other process that would cause this? If you don't know why then often you really shouldn't shrink if the log needs to be that size for some process. Growing and shrinking files over and over is not a good thing. You really want to understand why it grew and then you can figure out the best way to handle the size issue and size the log accordingly.

If the log grew do to some ad hoc, one off type of thing, you can't afford the disk space it uses and it won't grow like that ever again in your lifetime, then you may want to consider shrinking the file.

You said you tried to shrink the file but it didn't shrink. In that case, you would typically want to check:

SELECT log_reuse_wait_desc

FROM sys.databases

WHERE name = 'NameOfYourDatabase'

Sue